arkforge.tech valid

ArkForge

ArkForge builds verifiable trust infrastructure for AI agents. Trust Layer is a certifying proxy that generates cryptographically signed, publicly timestamped receipts for every API call made by an autonomous agent — across any model, any provider, any infrastructure.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T22:53:56.509Z. Cached copy · Source on arkforge.tech

# ArkForge

> ArkForge builds verifiable trust infrastructure for AI agents. Trust Layer is a certifying proxy that generates cryptographically signed, publicly timestamped receipts for every API call made by an autonomous agent — across any model, any provider, any infrastructure.

## What is ArkForge Trust Layer?

Trust Layer sits between an AI agent and any target API. For every transaction it:
- Proxies the call transparently (one line of code to integrate)
- Fingerprints the exchange (SHA-256) and signs it with ArkForge's Ed25519 key
- Anchors proofs in batches (100 proofs or 10 minutes): the batch root receives an RFC 3161 timestamp (FreeTSA, falling back to DigiCert or Sectigo; not eIDAS-qualified) and a Sigstore Rekor entry, the two witnesses independent of ArkForge
- Returns a Proof Triptych: machine-readable JSON (L1), HTTP headers (L2), human-readable HTML page (L3)
- Proof format and verification procedure: https://arkforge.tech/en/proof-spec.html

Every proof has a unique ID (e.g. `prf_20260914_194825_a747d0`) and is retrievable at `https://trust.arkforge.tech/v1/proof/{id}`.

## Key differentiator

AWS certifies AWS agents. Anthropic certifies Claude agents. OpenAI certifies GPT agents. Each creates a trust silo. ArkForge Trust Layer works across all of them in the same transaction chain — it is the only model-agnostic, provider-agnostic audit layer for multi-agent pipelines.

It is not a blockchain, not a payment protocol, and not tied to any AI vendor.

## Use cases

- **Provider disputes**: Show what an API actually returned, and when, if a call or its billing is contested
- **EU AI Act / NIST compliance**: Generate tamper-evident audit trails for AI systems under Article 12 (EU AI Act) and NIST AI RMF requirements
- **Multi-agent pipeline auditing**: Track which model called which API in complex agent chains (Claude → GPT → Mistral → custom API)
- **Receipt binding**: Bind the content hash of an external receipt to the proof of the call
- **Security forensics**: Reconstruct exactly what an agent did during an incident

## Technical facts

- Integration: `POST https://trust.arkforge.tech/v1/proxy` with header `X-Api-Key: your_key`
- Proof verification: `GET https://trust.arkforge.tech/v1/proof/{proof_id}`
- Witnesses: Ed25519 (ArkForge), RFC 3161 TSA (FreeTSA + DigiCert + Sectigo), Sigstore Rekor
- Latency overhead: ~200ms p50 vs direct API call
- Languages: any HTTP client (Python, Node.js, Go, curl…)
- No vendor lock-in: works with Claude, GPT-4, GPT-4o, Mistral, Llama, open-source models, any REST API

## Pricing

- **Free**: 500 proofs/month, no credit card required
- **Pro**: 29 EUR/month — 5,000 proofs/month
- **Enterprise**: 149 EUR/month — 50,000 proofs/month

API key: https://arkforge.tech/en/signup.html

## Pages

- [Homepage](https://arkforge.tech/en/index.html): What ArkForge does and why it matters
- [Pricing](https://arkforge.tech/en/pricing.html): Plans, proof volumes, FAQ
- [About](https://arkforge.tech/en/about.h
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=arkforge.tech · GET /v1/domain/arkforge.tech · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for arkforge.tech:
1. POST https://agentwebmap.com/v1/sites/arkforge.tech/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://arkforge.tech/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/arkforge.tech/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/arkforge.tech).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.