Developers

Connect one workflow. Follow one record through.

Send selected structured events from your application, inspect their processing status and export the evidence for independent verification.

Your first integration

Use the step-by-step quickstart or the official public repository for the Python client, retry queue and offline evidence verifier. The SDK is source-distributed alpha tooling. No wallet is required.

1. Create a workspace and project. Generate a scoped API key for the integration.

2. Choose the event. Identify a decision, outcome or control observation your team needs to review.

3. Assign a stable identity. Reuse the same event identity and content when retrying an uncertain submission.

4. Submit and inspect. Follow the record from acceptance through the available evidence stages.

5. Export and verify. Download the evidence bundle and check it against trusted verification material.

Acceptance is the first step

An accepted response confirms that the record has been durably accepted at the database boundary.

Log inclusion, checkpoint signing and any external timestamping follow separately. Their status remains visible, so an accepted record is not mistaken for a completed verification.

Retries without duplicate usage

An identical retry under the same scoped event identity returns the existing acceptance. It does not consume another receipt allowance.

Different content under the same identity is rejected. Keep the original identity and submission content when retrying.

Keep source material in your systems

Submit the supported structured fields needed for review. Keep source conversations, documents, media and raw tool inputs and outputs in your own systems.

Read the evidence design →