Developer integration

Bring independent evidence into the buyer workflow.

Use the existing Verify backend directly through HTTP or MCP. Assurance is the front door; Verify remains the evidence authority.

HTTP

Buyer Evidence API

Query observations for the exact route and HTTP method.

GET https://verify.atinamos.co.uk/v1/assurance/evidence
    ?endpoint=<absolute-url>
    &method=POST

MCP

Remote MCP

Connect a compatible MCP client directly to the Atinamos evidence service.

https://verify.atinamos.co.uk/mcp

RECEIPT

Signed Evidence Receipts

Retrieve the complete signed evidence document by receipt ID.

GET https://verify.atinamos.co.uk/v1/assurance/receipts/{receipt_id}

WEB

WebMCP / site tools

Assurance will expose a deliberately small read-only site-tool surface that reuses the same backend logic. Initial tools are planned for evidence lookup and signed receipt retrieval.

One evidence system. Assurance will not create a second evidence store, scoring system or interpretation layer.