Structured data, in minutes.
One authenticated call to the ORIS API turns a document into structured output — every result traceable to its job, reproducible by version. Nothing to install, nothing to host.
The ORIS API is paused for maintenance. Submissions return 503 service_maintenance while the pilot runtime is offline. Request pilot access and we will tell you when your key can run.
# contract — api.orves.ai · paused for maintenance # 1 · submit a document POST /v1/oris file=@contract.pdf # 202 · { "id": "prs_7d1…", "status": "queued" } # 2 · poll the job GET /v1/oriss/prs_7d1… # { "status": "completed", … } # 3 · fetch the structured result GET /v1/oriss/prs_7d1…/result # { "markdown": "# …" } # VERI API · MESH — in development
Small API. Deep guarantees.
| Area | What you get | Status |
|---|---|---|
| ORIS API | submit · poll · result — async, idempotent | in development · maintenance |
| VERI API | claims, evidence and spans inside a single source | in development |
| MESH | cross-source understanding over your Corpus — Web · API · SDK · MCP | in development |
| Python SDK | pip install orves — thin, typed, disposable by design | alpha · ORIS API in maintenance |
| OpenAPI spec | only implemented, served routes — versioned by date | not publicly served |
| Docs & API reference | markdown-first, agent-readable | in development |
| Playground | run real documents in the browser | planned |
Full status — what's shipped and what's next — on the roadmap.
Most parsers hand you JSON and a shrug.
A traditional parser
- document → JSON
- “trust me”
- no source spans
- no versions, no proof
When the output is wrong, you debug blind.
The Orves API
- document → structured output
- explicit, closed error vocabulary
- request IDs on every response
- failed work is never charged
Every response can be traced to its job and its version.
What the API promises — and shows.
Reproducible
Same input, same declared version, same output. Idempotency keys on every mutating call.
Retrievable
Completed results stay fetchable by job ID, and every response carries the request ID that ties it to logs and billing.
Honest failure
Jobs fail with an explicit reason from a closed vocabulary — never a silent partial result. Failed work is never charged.
Explicit limits
Rate limits, size limits and credit accounting are documented and enforced — 429s carry Retry-After, every response carries a request ID.