Developer Hub

Choose the boundary. Follow the proof.

Start with the software action you need to govern. Run a working shape, create one Decision Record, verify it, then request production access for that boundary.

Run the sandbox Open examples API reference Public catalog JSON

The shortest complete path

Each step has a public artifact. Production access comes after the request shape and proof model are clear.

1. BoundaryName one state-changing action.

2. ExampleStart from a working request shape.

3. SDK or HTTPSCall the server-side Decision API.

4. RecordStore verdict, evidence, and hashes.

5. VerifyCheck integrity and authenticity.

6. LaunchKey and meter the live boundary.

Enter by objective

The catalog routes to the existing deep references. It does not create pretend provider pages or duplicate the full documentation.

Gate an action

Choose a first-party boundary

OpenAI Decisions API vs Decide: choose model answers, Rulebook action gates, or combine them with the local integration recipe.

Pricing exceptions, refund review, agent tool actions, and CRM write-back are the maintained reference patterns.

Discount approval API Agent action gate Browse patterns Run proof

Integrate a system

Bind the decision to execution

Use CRM, billing, automation, queue, or agent guidance to preserve idempotency and record context through the state change.

Integration guides Code examples

Start from code

Install the shipped JavaScript client

The public npm package includes the client, types, verifiers, Rulebook v1 conformance runner, examples, and fixtures.

SDK contract npm package

Use MCP

Select the correct trust surface

Both surfaces belong to Decide. Policy Notaries is a standalone public, read-only service; Decision Runtime MCP handles customer-owned records in a separate private preview.

Compare MCP surfaces Policy Notaries

Verify proof

Check a record before relying on it

Use the hosted verifier, API, SDK, Ed25519 registry, or pinned trust material to verify Decision Records and packets.

Hosted verifier Verification docs

Review trust

Inspect operational evidence

Read the security boundary, live proof artifact, status packet, and changelog before production rollout.

Security Live proof Status

The same catalog is machine-readable

The public catalog names only implemented protocols, maintained reference patterns, public integrations, shipped SDK commands, and the current MCP visibility boundary.

Public catalog

curl https://www.decide.fyi/api/public/catalog

Well-known entry

curl https://www.decide.fyi/.well-known/decide.json

Static catalog MCP directory Policy Notaries server card OpenAPI LLM entry point Full LLM reference