Agent CertAgent Cert
Help

Frequently asked questions.

What is Agent Cert?

A third-party certification network for AI agent decisions. You submit execution metadata, we evaluate against your policy, sign the result with Ed25519, and anchor the hash to Solana. Customers / auditors / regulators can verify any receipt without an account.

Do you replace my agent platform?

No. Agent Cert is infrastructure around your agent. Your agent still runs on Bedrock / Copilot Studio / LangChain / whatever. We observe and certify; we don't orchestrate.

How does it cost work?

Every receipt = 3 Decision Credits. New accounts get 30 free credits (10 receipts) at signup. After that, top up via the CERT bridge at 1 CERT = 100 credits. No fiat path. See CERT & credits.

Is this on mainnet or devnet?

Devnet today. Mainnet launch is pending legal review of the CERT token economics and finalized treasury controls. The utility (Agent Cert) and the token (CERT) launch together at mainnet — the certification network runs the same on both, only the Solana cluster changes.

Can I verify a receipt without an account?

Yes. /r accepts a receipt ID from anyone, anywhere. The verify endpoint /v1/receipts/{id}/verify is also unauthenticated.

Is my prompt / agent output stored on-chain?

No. Only hashes are anchored to Solana. The actual execution metadata and evaluation output remain in our private database. The on-chain memo is small (receipt_id, execution_hash, evaluation_hash, issuer reference, timestamp).

What happens to my data if you go out of business?

Off-chain receipts live in our Postgres database. On-chain anchors live on Solana forever — even if we vanish, the hashes are still publicly verifiable. We'd publish the issuer public key (already published at /.well-known/agent-cert-pubkey) and the Postgres dump so any third party can complete the verification chain.

How is the MCP server secured?

Every request to /mcp/sse requires X-API-Key. No anonymous access. Revoking a key at /settings/api-keys immediately invalidates any active MCP session. Tools are scoped to the calling account via a server-side contextvar — non-admins cannot see other users' receipts. See MCP Server reference.

Which LLM does the evaluator use?

Qwen 32B Instruct, self-hosted in Azure. We deliberately use a permissively-licensed open-weight model so we can host it ourselves (no third-party data sharing) and so the network isn't locked to any one vendor.

Can I run my own evaluator?

Not in v1. The network operates a single evaluator stack so receipts are interoperable. A federated / verifier-network mode is in Phase 2 — see certnetwork.net/network.

What does my Free Trial cover?

30 credits = 10 fully-evaluated, fully-anchored Decision Receipts. Use them on real production traffic — they're indistinguishable from purchased receipts.

How do I get more credits?

Acquire CERT on the open market (Raydium, Orca, supported CEX), send it to the Treasury wallet shown at /credits. The backend credits your balance at 1 CERT = 100 credits after Solana finality.

Can I get a refund?

Operational corrections (a clear platform error on our end) result in a credit refund to your ledger. We do not redeem CERT back to fiat — the bridge is one-way by design.

Do you support webhooks?

Not in v1. Receipts are returned synchronously from the API call; anchoring is async but polled via /v1/receipts/{id}/anchor. Webhooks (for anchor completion, low-credit alerts, key rotation) are on the roadmap.

What's your privacy posture?

Execution metadata you send is stored in our private Postgres. Only hashes hit the public ledger. We do not share metadata with third parties. Customers / enterprises that need additional protections (confidential evaluation, private deployment) — that's a Phase 2 capability.

Who's behind Agent Cert?

Operated by Prava Labs, LLC. The CERT token is issued under the same entity. See certnetwork.net for the full entity / governance / tokenomics picture.

Where do I report bugs / vulns?

Email security@agentcert.net for security issues; the public verifier at /r for receipt-level verification failures (those go straight to the eng team).