Completed, non-test paid tool calls recorded since service tracking began.
CURRENT GATEWAY CHECK
The gateway is responding.
This page separates what the service can prove from what it does not yet claim, with privacy-safe operating evidence for people and agents.
PUBLIC OPERATING EVIDENCE
Trust should be inspectable.
These are aggregate outcomes recorded by the service. They reveal no wallet, payer, agent, transaction, revenue, or request-content details.
Paid successes divided by paid successes plus recorded service errors—not an uptime SLA.
Publicly recorded service incidents that have not been marked resolved.
The most recent completed, non-test paid tool call recorded by the service.
30-DAY HISTORY
Daily observed outcomes.
Gold bars show successful paid calls. A red marker shows one or more recorded service errors. An empty day means no qualifying outcome was recorded; it does not prove downtime.
METHODOLOGY
What this evidence means.
- A successful paid call completed the application route after payment validation.
- A recorded service error is an application-level failure captured while handling a tool request.
- Test traffic is excluded from the paid-call total.
- Counts come from first-party service events and are updated as the application records them.
Independent availability checks: GitHub Actions tests the public status, trust, discovery, MCP, and x402 boundaries every 15 minutes. Its public run history is evidence of those checks, not a contractual uptime SLA.
Inspect the machine-readable trust evidence →SECURITY & ACCOUNTABILITY
Claims with boundaries.
The latest supplied platform assessment, dated September 7, 2026, reviewed the public security and discovery surface. The assessment itself is not published here and is not represented as an independent certification.
- Public-network fetch controls
- Active
- Privacy-safe funnel attribution
- Active
- Repository identity separation
- Active
- Independent availability checks
- Every 15 minutes
- Contractual uptime SLA
- Not claimed
CURRENT CAPABILITY
8 paid routes, stated precisely.
The live gateway exposes these account-free HTTP tools with explicit x402 terms. This confirms current advertising and reachability; it does not claim that an end-to-end settlement occurred at this page-render timestamp.
/api/merchant-snapshotAdvertised/api/treasuryAdvertised/api/payment-guardAdvertised/api/verifyAdvertised/api/batchAdvertised/api/base-balanceAdvertised/api/checkAdvertised/api/merchant-auditAdvertised