Quickstart

The 60-second test: install the SDK in your language of choice, run the conformance suite, see the 59 canonical fixtures pass. If they pass on your machine, you’ve proven byte-for-byte interop with every other Ratify implementation.

# Install as a module in your project
go get github.com/identities-ai/[email protected]

# Or clone and run the full conformance suite
git clone https://github.com/identities-ai/ratify-protocol
cd ratify-protocol
go test ./...
# → ok  github.com/identities-ai/ratify-protocol  0.5s

Full Go quickstart →

npm install @identities-ai/[email protected]

Or run the conformance suite yourself:

git clone https://github.com/identities-ai/ratify-protocol
cd ratify-protocol/sdks/typescript
npm install
npm test
# → 101 passed  (59 conformance fixtures + cross-SDK vectors + levers + providers)

Full TypeScript quickstart →

pip install ratify-protocol==1.0.0a10

Or run the conformance suite yourself:

git clone https://github.com/identities-ai/ratify-protocol
cd ratify-protocol/sdks/python
pip install -e '.[dev]'
pytest -q
# → 102 passed  (59 conformance fixtures + 43 unit tests)

Full Python quickstart →

cargo add [email protected]

Or run the conformance suite yourself:

git clone https://github.com/identities-ai/ratify-protocol
cd ratify-protocol/sdks/rust
cargo test
# → test result: ok. 1 passed (loads all 59 fixtures)

Full Rust quickstart →

Download the pre-built library for your platform from the GitHub Releases page — no Rust toolchain required. The ratify.h header is also committed at sdks/c/include/ratify.h.

Or build from source (requires Rust 1.70+):

git clone https://github.com/identities-ai/ratify-protocol
cd ratify-protocol/sdks/c
cargo build --release
# → target/release/libratify_c.a + libratify_c.so + include/ratify.h

Run the conformance suite:

cargo test --test conformance
# → 59/59 conformance fixtures pass
cargo test --test api
cargo test --test advanced
# → 58 ABI unit tests pass across api + advanced

Full C/C++ SDK guide →

What “the conformance suite” means

Every Ratify SDK ships a test that loads testvectors/v1/*.json — 59 fixtures generated deterministically by the Go reference implementation — and verifies each one. The fixtures cover:

Valid delegations of various scopes, durations, and chain depths
Tampered delegations (modified scope, modified expiry, modified subject)
Expired certs (clock-skew scenarios)
Out-of-scope requests (requested scope not granted by chain)
Revoked certs (against signed revocation lists)
Hybrid signature edge cases (Ed25519 valid + ML-DSA-65 invalid, both invalid, etc.)
Sub-delegation chains (Alice → Agent-A → Agent-B)
Constraint enforcement (geo, time, version)

If all 59 pass in your SDK, your SDK produces and verifies the same bytes as every other Ratify SDK on the planet. That is the interoperability contract.

Run the end-to-end demo

The conformance suite proves the bytes are correct. The demos prove the protocol does what it claims. Each runs nine scenarios — five positive (authorized → verified), four negative (tampered / out-of-scope / expired / revoked) — and prints what happened and why.

cd ratify-protocol
go run ./demos/go

Python

cd sdks/python && pip install -e . && cd ../..
python demos/python/demo.py

TypeScript

cd sdks/typescript && npm install && npm run build && cd ../..
cd demos/typescript && npm install && npm run demo

Rust

cargo run --manifest-path demos/rust/Cargo.toml

C / C++

cd ratify-protocol/sdks/c
cargo build --release
cc examples/verify_bundle.c -I include \
    -L target/release -lratify_c -lpthread -ldl \
    -o verify_bundle && ./verify_bundle

The narrative demos are a single repository directory for Go, TypeScript, Python, and Rust. The C/C++ path uses the ABI example in sdks/c/examples/. Reading one demo and watching it run is the fastest way to understand what the protocol does.

Next steps

Want to ship an integration? Start with the language-specific guide (Go / TypeScript / Python / Rust / C/C++).
Building for embedded or Physical AI? The C/C++ SDK ships libratify_c.a for RTOS and embedded Linux targets.
Want to understand the protocol? Concepts: Delegate, Present, Verify.
Building a surface-specific integration? Jump to the integration guides.
Need managed revocation and audit? Ratify Verify overview.