Docs / Recipes

// RECIPES

Per-framework quickstarts

One copy-paste recipe per stack. Each is a single screen: install, point at Agentics, run one call, and read the verifiable x-agentics-receipt. Every recipe below uses the canonical gateway at https://agentics.you/api/v1 (native ingress for the Anthropic and Gemini SDKs) with your AGENTICS_API_KEY.

Two integration patterns

Pattern A

Full governance — route through the gateway

Swap one base_url so your calls travel through Agentics. They are routed, budgeted, and guarded inline, and the Proof Ledger writes one verifiable receipt per call, returned in the x-agentics-receipt response header. Every recipe in this library is Pattern A.

Pattern B

Observe-only — emit a receipt after the fact

Your app calls its provider directly, then emits a receipt to Agentics afterward. There is no inline governance — you get the proof trail without changing the call path. Use it when you cannot route traffic through the gateway; see the SDK track() flow.

Language SDKs

OpenAI-compatible base-URL swaps against /api/v1, plus native ingress for the Anthropic and Gemini SDKs.

Anthropic SDKPattern A · native Gemini SDKPattern A · native GoPattern A · base-URL JavaPattern A · base-URL .NETPattern A · base-URL RubyPattern A · base-URL

Agent frameworks

One config line points the framework's OpenAI client at the gateway; the rest of your code is unchanged.

LangChainPattern A LlamaIndexPattern A LiteLLMPattern A Vercel AI SDKPattern A OpenAI Agents SDKPattern A CrewAIPattern A HaystackPattern A DSPyPattern A AutoGenPattern A

Coding agents

Wrap the terminal tool's traffic with agentics capture — no code changes.

Claude CodePattern A · capture Codex CLIPattern A · capture
New here? Start with the 5-minute quickstart to create an ak_ key, then pick your recipe above.
Quickstart Verify a receipt →