AxonGate

AxonGate is an evidence trust layer for AI agents. It checks whether public web sources actually support a claim, flags weak or noisy pages, and returns citation-ready trust decisions before an agent cites or acts.

Service Contract

Pricing

The recommended tier for production agent calls is fresh. Starter is available for first paid conversion on the sample target or existing cache; cached, basic, fresh, and deep cover repeat reads and live supplier-backed workloads.

Source Trust Reports

Source Trust Reports, still called Proof Packs in the API, are paid evidence checks for agent builders. Use them before RAG ingestion, web citations, autonomous actions, or customer-facing answers. They return whether the source supports the claim, what evidence is usable, and what risks make the source weak.

Successful paid reports are retained for 30 days. Store report_id, report_url, verify_url, result_hash, source_hash, agent_action, and source_quality_score. Use verify receipts for hash and retention checks, follow-up for no-spend reuse, and refresh quotes when recency or missing evidence matters.

curl "https://api.axongate.one/v1/proof-pack/sample?source=docs"

Mini preview page: https://api.axongate.one/proof-pack/preview

curl "https://api.axongate.one/v1/proof-pack/preview?target_url=https%3A%2F%2Fwww.iana.org%2Fdomains%2Freserved&pack=quick&source=docs"

Quote page: https://api.axongate.one/proof-pack/quote

curl "https://api.axongate.one/v1/proof-pack/quote?target_url=https%3A%2F%2Fexample.com&pack=standard&source=docs"

Quote responses include a retained quote_id, a resume page at https://api.axongate.one/checkout/{quote_id}, and a receipt API at https://api.axongate.one/v1/quotes/{quote_id}. Quote receipts are retained for 7 days.

Payment confidence page: https://api.axongate.one/checkout/confidence

curl "https://api.axongate.one/v1/checkout/confidence?product=proof_pack&target_url=https%3A%2F%2Fexample.com&pack=standard&source=docs"

Post-payment reuse APIs:

curl "https://api.axongate.one/v1/proof-pack/reports/{report_id}"
curl "https://api.axongate.one/v1/proof-pack/reports/{report_id}/verify"
curl -X POST "https://api.axongate.one/v1/proof-pack/reports/{report_id}/follow-up" \
  -H "Content-Type: application/json" \
  -d '{"question":"Can my agent cite this claim?"}'
curl -X POST "https://api.axongate.one/v1/proof-pack/reports/{report_id}/refresh"

No-spend retained report sample:

curl "https://api.axongate.one/v1/proof-pack/reports/ppr_sample_source_trust"
curl "https://api.axongate.one/v1/proof-pack/reports/ppr_sample_source_trust/verify"
curl -X POST "https://api.axongate.one/v1/proof-pack/reports/ppr_sample_source_trust/follow-up" \
  -H "Content-Type: application/json" \
  -d '{"question":"Can my agent cite reserved domains?"}'
curl -X POST "https://api.axongate.one/v1/proof-pack/reports/ppr_sample_source_trust/refresh"

Request capture page: https://api.axongate.one/proof-pack/request

curl -X POST "https://api.axongate.one/v1/proof-pack/leads" \
  -H "Content-Type: application/json" \
  -d '{
  "contact": "builder@example.com",
  "target_url": "https://example.com/source",
  "question": "Which claims can my agent cite from this source?",
  "pack": "quick",
  "use_case": "RAG evaluation",
  "budget_usdc": "10/month",
  "source": "docs"
}'

Private lead and order consoles require AXONGATE_OPERATOR_TOKEN and are reached from the operator dashboard after authentication. Optional notifications use AXONGATE_PROOF_PACK_LEAD_WEBHOOK_URL.

{
  "target_url": "https://example.com/source",
  "question": "What does this source establish?",
  "pack": "standard",
  "force_refresh": false
}

curl -X POST https://api.axongate.one/v1/x402/proof-pack?pack=standard \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <x402-payment-proof>" \
  -H "X-AxonGate-Pack: standard" \
  -d '{"target_url":"https://example.com/source","question":"What does this source establish?","pack":"standard","force_refresh":false}'

Evidence Bundles

Evidence Bundles, still called Proof Bundles in the API, answer a higher-value question: can this group of public sources prove the claim well enough for an agent to cite it? The quote page includes a tracked checkout redirect; configured payment links send buyers to payment, while unconfigured bundles fall back to request capture.

Bundle page: https://api.axongate.one/proof-pack/bundle

Bundle confidence page: https://api.axongate.one/checkout/confidence

Tracked checkout route: https://api.axongate.one/proof-pack/bundle/pay. Configure payment URLs with AXONGATE_PROOF_BUNDLE_SCOUT_PAYMENT_URL, AXONGATE_PROOF_BUNDLE_BUILDER_PAYMENT_URL, and AXONGATE_PROOF_BUNDLE_AUDIT_PAYMENT_URL.

Stripe fulfillment webhook: configure the private Stripe endpoint path in the Stripe Dashboard, send checkout.session.completed, checkout.session.async_payment_succeeded, and checkout.session.async_payment_failed, then set AXONGATE_STRIPE_WEBHOOK_SECRET from the Stripe signing secret.

Stripe Payment Links should redirect after payment to https://api.axongate.one/proof-pack/bundle/delivery?session_id={CHECKOUT_SESSION_ID}. The webhook still handles fulfillment if the buyer closes Stripe before redirecting, and buyers can recover delivery at https://api.axongate.one/proof-pack/bundle/recover with their checkout email and one submitted target URL.

Email delivery uses Resend when configured. Set AXONGATE_EMAIL_DELIVERY_ENABLED=true, AXONGATE_EMAIL_FROM=AxonGate <reports@axongate.one>, and AXONGATE_RESEND_API_KEY; fulfilled Proof Bundles email the customer a delivery link and concise report summary.

curl "https://api.axongate.one/v1/proof-pack/bundle/quote?target_urls=https%3A%2F%2Fwww.iana.org%2Fdomains%2Freserved%0Ahttps%3A%2F%2Fexample.com&bundle=scout&source=docs"

curl -X POST "https://api.axongate.one/v1/proof-pack/bundle/leads" \
  -H "Content-Type: application/json" \
  -d '{
  "contact": "builder@example.com",
  "target_urls": [
    "https://www.iana.org/domains/reserved",
    "https://example.com",
    "https://example.org"
  ],
  "question": "Which claims can our agent safely cite across these sources?",
  "bundle": "builder",
  "use_case": "Agent launch due diligence",
  "budget_usdc": "20/month",
  "source": "docs"
}'

Standard x402 Flow

1. Use /v1/x402/quote?target_url=... to choose the cheapest safe tier before spending.
2. Probe /v1/x402/access or read /.well-known/x402 to discover payment requirements.
3. Create an x402 payment proof for the selected tier and Base USDC amount.
4. POST a JSON body with target_url, optional tier, and optional force_refresh.
5. Send the proof in PAYMENT-SIGNATURE. AxonGate verifies payment, margin, target safety, and then fetches clean markdown.

Free Quote

The quote endpoint validates a public target URL, checks whether the starter sample or cache is immediately available, returns exact x402 amounts for every tier, and emits a ready buyer command. It does not trigger supplier work or spend USDC.

curl "https://api.axongate.one/v1/x402/quote?target_url=https%3A%2F%2Fwww.iana.org%2Fdomains%2Freserved&source=docs"

Request Body

{
  "target_url": "https://example.com/source",
  "tier": "fresh",
  "force_refresh": true
}

Example

curl -X POST https://api.axongate.one/v1/x402/access \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <x402-payment-proof>" \
  -d '{"target_url":"https://example.com/source","tier":"fresh","force_refresh":true}'

Retry Credits

If payment succeeds but a retryable supplier or network outage prevents delivery, AxonGate can return 503 with X-AxonGate-Retry-Credit. The client can call /v1/x402/retry with the same request body and the retry credit, without paying twice.

Supply Guards

AxonGate rejects unsafe targets before payment-funded supplier work, blocks private and loopback address space, follows bounded redirects, caps content size, rate-limits abuse patterns, and fails closed when dynamic gas pricing or supplier availability would make delivery uneconomic.