Build With
MOCHI
● DEVELOPER DOCUMENTATION
1:
Start With A Schema
Description
The planned API accepts a source document, schema version, jury size and disclosure preferences. The specification below defines the intended integration. The current workspace supports local previews.
| Schema | Fields |
|---|---|
| EX_DIVIDEND | Ticker, dates, amount and multiplier effect |
| SPLIT | Ratio and effective date |
| EARNINGS | EPS, revenue and source comparisons |
| RESERVE_ATTESTATION | Issuer, reserves, supply and as-of date |
| NAV | Fund, shares and net asset value |
| INVOICE | Payee, amount, currency and due date |
| FREEFORM_FACT | Question, answer and required evidence |
2:
Integration Surface
Description
POST /v1/query
{ schema, document, jurySize, privacy }
GET /v1/verdict/:id
GET /v1/feeds/:feedId/:key
GET /v1/disagreement?schema=EARNINGSProduction requests require authenticated ownership, encrypted document transport, verified payment and an idempotency key. Access rights and settlement must be validated for each request.
Each result must identify its source, schema version, model set, evidence, dissent, receipt status and timestamp. Attestation status must be explicit.
Try the local workspace →
Work With Evidence