How Chitmark works

Three workflows for screening costly actions, controlling paid access, and recognizing enrolled agents.

Choose a workflow

Trust Decisions

Screen costly actions before granting value.

  1. Request

    Your app receives a signup, trial, or other costly request.

  2. Verify

    Send the action and context to POST /v1/verify.

  3. Decision

    Read one verdict: allow, challenge, or deny.

  4. Enforce

    Your app grants value, requires step-up, or stops the action.

  5. Feedback

    When the outcome is known, report it on the stored eventId.

For a free trial, check the request before issuing credits. Hold the grant during step-up or if verification is unavailable.

Use it for Signup abuse, trial and credit farming, costly account changes, and API-key issuance.

Verify your first action

Agent Paid Access

Sell controlled access to API resources.

  1. Quote

    The buyer requests fixed terms for a seller-configured resource.

  2. Accept

    The buyer accepts before expiry, within its spending ceiling.

  3. Authorize

    The payer completes checkout. The seller checks local permission and reserves execution after confirmed capture.

  4. Deliver

    Your backend serves the resource within the granted reservation.

  5. Report

    The seller records the execution result and units used.

For a paid dataset lookup, use POST /v1/charge to manage the purchase. Release the lookup only when the seller has a fresh reservation for that operation.

Use it for Fixed-price API calls, bounded dataset access, and prepaid compute with enforced deadlines.

Try the paid access integration

Agent Attribution

Recognize enrolled agents with fresh signed proof.

  1. Session or request

    Start with an exact site origin and a server-selected session credential or agent proof.

  2. Gather evidence

    Attach a fresh proof from an enrolled agent or supply a site session.

  3. Verify evidence

    Resolve checks the enrolled key and the signature for this recipient.

  4. Read the result

    An enrolled network agent can match as verified_agent_account. Principal details require a current grant for the recipient and purpose.

An enrolled assistant can sign one proof for Site A and another for Site B. Both sites can recognize the agent and receive distinct subjects.

Use it for Cross-site recognition with fresh proof, site session continuity, and authorized principal attribution.

Explore Agent Attribution

Make your first request

Choose a product to see its endpoint and setup.

POST /v1/verify

A server-side API key with verify:write. Add feedback:write to report outcomes.

Verify your first action

Keep control at your application boundary

Your app holds the action when a verdict is unavailable, withholds paid resources without a valid reservation, and applies its own authorization policy to attribution evidence.

Trust Decisions failure behavior

The four checkpoints can share one server-side record: resolve the actor, decide the action, confirm payment, then execute. See the composed transaction and what is still manual today.