Om API Documentation

Launch model workflows, retrieve Generated Data from Data Generation orders, and run diligence research through Om API.

Authentication

Most requests require either `x-api-key` or an OAuth bearer token.

API keys remain the canonical external SDK and script path
OAuth bearer tokens are supported for user-scoped integrations
Health checks at /v2/health are public
Use idempotency keys on job-launch and JSON POST routes

Open section

Wallet Credits

Track available Wallet Credits and inspect route pricing before you launch work.

Wallet Credits are USD-denominated (1 Wallet Credit = $0.01 USD)
Use /v2/credits to check available Wallet Credits
Current pricing manifest at /v2/pricing

Open section

Generated Data

Export Generated Data shards from qualifying Data Generation output.

Data Generation output access
Generated Data discovery via /v2/datasets/catalog
Signed URL exports for large-scale pulls

Open section

Diligence

Run target research workflows from source discovery to synthesis.

Asynchronous endpoints return 202 with job_id
Track status via /v2/jobs/{job_id}
Deep diligence results live at /v2/jobs/deep-diligence/{job_id}
Synthesis results live at /v2/jobs/synthesizeReport/{job_id}

Open section

Molecule Fulfillment

Search OnePot-backed availability, quote provider-backed Molecule Fulfillment, create invoice-backed fulfillment orders, and inspect fulfillment orders.

Search availability through /v2/molecules/search
Quote exact-match molecules through /v2/molecules/quote
Invoice and order-status routes stay user-scoped
SDK helpers are available under client.molecules

Open section

Om MCP

Bring Diligence, Data Access, Jobs, Artifacts, and Hub workflows into Codex, Claude Code, and other MCP clients.

Hosted remote MCP setup
Codex and Claude Code HTTP config examples
Practical use cases for agentic research and workflow orchestration

Open section

Base URL

All examples assume a base URL of https://api.omtx.ai.