Your agents — Claude, GPT, Mistral, your internal APIs — execute thousands of API calls. When a provider denies delivery or a client disputes the charge: who has proof?
See a live proof →Provider says it wasn't delivered. You can't prove otherwise.
Your agent did the work, but the client denies it. Without a signed proof, it's your word against theirs.
Regulator wants records. You have logs, not proof.
Your agent orders 1 server. The vendor bills you for 19. Without a neutral proof, it’s your word against theirs. With ArkForge, it’s resolved in 5 seconds.
Without ArkForge
Lawyers. 6 weeks. Invoice paid.
With ArkForge
Dispute resolved in 5 seconds. Invoice rejected, case closed.
Why the proof is bilateral
The proof is created after the vendor responds — it seals both sides of the exchange. If the vendor bills 19 but responded “1 confirmed”, their own response contradicts them. Not your logs. Their response.
€0.01 per proof. One avoided dispute saves thousands.
One API call. Three things happen.
The request transits through Trust Layer. Included in your monthly quota — Free (500), Pro (5,000), Enterprise (50,000).
Request relayed to target API. Response fingerprinted (SHA-256).
Ed25519 signed. RFC 3161 timestamped.
Even if ArkForge disappears tomorrow, your proofs remain verifiable. Optionally add external payment verification for a 4th layer of trust.
Origin authentication. Every proof is signed with ArkForge's Ed25519 key. The public key is published and verifiable by anyone.
Certified timestamp from a pool of WebTrust-certified authorities (FreeTSA → DigiCert → Sectigo). eIDAS-qualified QTSP available on request for legal proceedings requiring qualified timestamps.
Immutable transparency log entry. Every proof is appended to Sigstore's public Rekor ledger — tamper-evident and independently auditable by anyone.
Optional: External Payment Verification
Attach a Stripe receipt URL to your request. ArkForge fetches it, hashes the content (SHA-256), and binds it to the proof chain hash. The receipt becomes a 4th independent witness — tamper-proof and verifiable by anyone.
You’re building an agent
Your agent calls Claude, GPT, Mistral, internal APIs, third-party services — often in the same chain. No provider certifies that chain. ArkForge certifies every hop, regardless of model or infrastructure.
Zero SDK. Two lines. Works with LangChain, AutoGen, CrewAI, or a raw HTTP call.
Not a payment protocol
Some “trust layers” handle payments between agents. ArkForge is different: it’s a certifying proxy that sits between your agent and any API — proving what was sent, what was received, and when. Model-agnostic, provider-agnostic, infrastructure-agnostic. The proof works across Claude, GPT, Mistral, open-source models, and any REST endpoint — in the same chain.
Which model was called? Exact prompt? Exact response? Real cost? Agent logs are mutable. ArkForge proofs are not.
DORA, NIS2, EU AI Act require verifiable proof — not logs. ArkForge certifies every execution with a qualified timestamp and anchors it in a public immutability log.
Real proof — hashes, Ed25519 signature, RFC 3161 timestamp, Sigstore Rekor entry.
Python, TypeScript, Rust, Go — it doesn’t matter. LangChain, AutoGen, CrewAI, Semantic Kernel, or raw HTTP calls — it doesn’t matter. If your agent makes HTTPS calls, Trust Layer integrates in two lines.
No dependency to install. One header, one URL. Works with any existing HTTP library.
The original response is returned in full inside service_response.body. The proof sits alongside it — your agent extracts what it needs.
The proof is returned in the response body. Your agent can forward it, store it, or ignore it — your choice.
Dogfooding
ArkForge is operated by an autonomous AI system. Every GitHub response, every X post, every external decision by the CEO is certified by the product it operates — cryptographic proof anchored in Sigstore Rekor.
See a real CEO proof →Every transaction proven. Every dispute won in advance.