How can we help?

Trust Layer is a certifying proxy that sits between your AI agent and any target API. It forwards the request and generates a cryptographic proof: an Ed25519 signature by ArkForge, then an RFC 3161 timestamp and a Sigstore Rekor entry that are independent of ArkForge.

No. Trust Layer uses Stripe for prepaid credit purchases on the Pro plan, but its value is proof generation. Stripe handles billing, not proof witnessing.

Send a POST request to the /trust/v1/proxy endpoint with your API key, plan identifier, and target URL. Trust Layer handles everything else — payment, forwarding, and proof generation. See the documentation for details.

Ed25519 signature, made with ArkForge's own key, guarantees the proof was issued by ArkForge (public key published). It is not independent of ArkForge. Proofs are anchored in batches (every 100 proofs or 10 minutes): the batch root is submitted to the RFC 3161 TSA pool (FreeTSA → DigiCert → Sectigo) for a certified timestamp proving the batch existed at a specific moment; the first available server wins, provider recorded per proof. Platform keys use DigiCert directly, bypassing FreeTSA. eIDAS-qualified QTSP available on request. The same batch root is also appended to Sigstore Rekor, a public transparency ledger, independently auditable by anyone. Only the RFC 3161 timestamp and the Rekor entry can be verified without trusting ArkForge.

No. ArkForge does not delete proofs during their retention period. Once a proof's batch is anchored (within 10 minutes), any change to its committed data breaks its timestamp and Rekor entry, including a change made by ArkForge. Only informational metadata such as the dispute status can change.

Every proof is delivered in three formats: L1 Digital Stamp (JSON for machines), L2 Ghost Stamp (HTTP headers for automated pipelines), and L3 Visual Stamp (HTML page for humans). All three contain the same proof data.

Every proof has a public URL (e.g. /trust/v1/proof/prf_...). You can also recompute the SHA-256 hash of the original payload and compare it with the hash in the proof.

End-to-end latency is under 1 second, including request forwarding and proof generation with all witnesses.

The Free plan includes 500 proofs/month at no cost. Pro: 5,000/month (29 EUR). Enterprise: 50,000/month (149 EUR). Platform: 500,000/month (599 EUR) with DigiCert timestamping. See the Pricing page for details.

Ed25519 is always present. The RFC 3161 TSA pool (FreeTSA → DigiCert → Sectigo) provides automatic failover — if FreeTSA is unavailable, DigiCert or Sectigo takes over within the same request. The timestamp_authority.provider field in the proof records which server was used.

ArkForge infrastructure is hosted in France (European Union). All data processing is GDPR-compliant. See our Privacy Policy for details.

No. Trust Layer stores SHA-256 fingerprints (which are not personal data) and transaction metadata. The agent identity (X-Agent-Identity) is optional.

Visit the signup page for your target plan: Pro (5,000 proofs/month), Enterprise (50,000/month), or Platform (500,000/month — with DigiCert timestamping). Billing is handled via Stripe.

Go to the billing management page, enter your API key, and you will be redirected to the Stripe Customer Portal where you can update your payment method, view invoices, or cancel your subscription. Cancellation takes effect at the end of the current billing period. The Free plan has no subscription — no action needed.

If a transaction produced an incorrect result, either party (buyer or seller) can file a dispute via POST /v1/disputes. The dispute is recorded and shown on the proof; ArkForge does not arbitrate it. Anti-abuse limits apply: 1-hour cooldown between disputes, 7-day filing window, one dispute per proof.

Yes. A dispute does not invalidate the cryptographic proof — the chain hash, signature, and timestamps remain intact. The dispute adds metadata (disputed, dispute_id) to the proof, which is visible on the public verification page. The proof's committed data does not change.

Yes. The code is licensed under MIT, and the specification under CC BY 4.0. Visit our GitHub repository to inspect, audit, or contribute.