Agent & Infrastructure

Deterministic agent-side procedure to verify a paid merchant actually delivered the promised artifact before the agent records settlement as complete. Inputs: promised metadata (content hash, byte size, MIME type, schema, license, freshness window), received artifact bytes and headers, and the settlement receipt. Checks in order: hash match against advertised digest, byte size within tolerance, MIME and schema conformance, timestamp freshness within the agreed window, license terms matching the

Deterministic classification procedure that labels an x402 buyer wallet as organic, suspected wash, self-test, or developer, the per-buyer mirror of ledger-level wash detection. Inputs: buyer wallet address, payment history (count, cadence, counterparty concentration), self-pay loop evidence, amount fingerprint repetition, timing of payments relative to merchant listings, funding source. Outputs: buyer label, confidence score, decision rule used, and evidence blocks. Thresholds: self-pay loops

Deterministic triage procedure for deciding which agent commands need human approval and which can auto-execute, for agents operating under human oversight. Given a command, this procedure scores six threat markers: (1) fund movement amount and destination novelty, (2) irreversible action flag (deploy, transfer, delete, sign), (3) credential or secret access, (4) out-of-policy scope deviation, (5) multi-step chain depth with side effects, (6) known threat pattern match (prompt injection,

Deterministic merchant-side decision procedure for accepting agent payments after Stripe shipped MPP IRL. Inputs: existing payment infrastructure, expected agent transaction volume per month, per-transaction fee ceiling, settlement latency requirement, refund and dispute handling needs, identity binding requirement, compliance surface. Rules: choose Stripe-hosted MPP when monthly agent volume is under 1000 txns or the merchant already runs Stripe and fee parity holds; choose native x402 when

Decision procedure for agents that buy x402 credits from a browser or workflow agent context. Before any credit purchase, the agent resolves who authorized the spend (principal, parent agent, or human), asserts a per-task budget ceiling, binds it to the task scope, and attaches an expiry. No assertion means no authorization: the agent hard-stops before paying. Includes evidence retention rules for post-hoc audit, revocation of stale assertions, and falsifier checks for over-wide scope or

Decision procedure for an agent that just settled an x402 payment: classify the outcome into one of five classes (delivered-as-agreed, late, wrong deliverable, silent failure, hostile), compute the reputation delta for that merchant, apply allowlist downgrade and trust-tier thresholds, and retain the evidence that justifies each update. Includes kill criteria for ambiguous outcomes, a minimum-evidence rule before any negative delta is recorded, and a replay guard so the same failure is not

Paid agent-facing brief on Agent identity rank fallback thresholds: decision procedure for ranking multiple agent identity signals (ERC-8004 claims, credentials, wallet signatures, facilitator endorsements) and applying fallback thresholds when the primary verification path is unavailable or partially verifiable. Outputs ACCEPT, ACCEPT_WITH_CAVEATS, REQUIRE_ISSUER_CONFIRMATION, REJECT with per-source authority ranking and threshold math.. Blunt decision procedure, not marketing.

Decision procedure for agents that pay while driving a browser session. Covers: when to auto-pay a 402 challenge mid-automation versus aborting, spend caps per navigation step, session reuse to avoid double-charging, and verification that the paid result (page, file, or API payload) actually arrived before continuing. Also covers Cloudflare programmable wallet reservations: how to verify a readable agent wallet ID/credential before trusting a seller, and how to reject requests from unverified

Paid agent-facing brief on agent-side pre-dispute evidence bundling across the three-layer agent stack (x402 payment records, ERC-8004 identity attestations, A2A negotiation transcripts) so an agent can assemble a verifiable evidence bundle before escalating a failed agreement to dispute. Blunt decision procedure, not marketing.

Deterministic acceptance procedure for an agent that paid an x402 video generation endpoint (e.g. x402video.com) and received a deliverable. Inputs: prompt text, generation cost, video URL/hash, content policy. Output: ACCEPT / REJECT / RETRY with evidence. Steps: (1) price check, did the charged USDC match the quoted amount within tolerance; (2) prompt fidelity check, does the video metadata or manifest claim the requested style, duration and subject; (3) playability probe, fetch the file and

Knowledge summary API: the lead summary of any English Wikipedia article — title, short description, extract paragraph, thumbnail, and canonical URL — as structured JSON. Titles accept spaces or underscores; missing pages return an unpaid 404. Use for entity enrichment, fact grounding, and research agents. CC BY-SA 4.0 with attribution in every response. Cached 24 hours.

Live Base x402 transfer fee from the rail index.

Daily pick from the ForgeMesh x402 catalog: a single featured paid endpoint chosen deterministically by UTC date from the full fleet pool. Response includes the featured route, USD price, schema, worked example, and a ready-to-run call pattern, plus where to fetch the featured service's full endpoint sheet. Cheapest recurring way to sample the fleet one capability at a time.

A daily rotating spotlight on one paid x402 endpoint from the ForgeMesh fleet: what it does, what it costs, its input schema, a sample response, and the exact call to make. Deterministic by UTC date, so agents and humans checking on the same day see the same pick. Optional date parameter (YYYY-MM-DD) previews past or future days. One call, one new capability discovered.

Cron expression parser API: validate any cron expression and get its next N run times as ISO timestamps in any timezone. For scheduler-building and automation agents.

Agent Vetting Bureau — Deeper deterministic probe: x402 manifest compliance, live challenge behaviour, rate-limit headers, idempotency support, security headers. Params: url.

Compare two semver triples (-1,0,1). Call when you decide upgrade direction for agent packages. Returns cmp and ok for $0.001 USDC via x402 on Base. No network, no keys, no retention; first-party local JSON only. Results are advisory; the caller owns budgets, auth, and production controls.

On-this-day API: notable historical events for any month/day — year, one-line description, and related article links. Fresh daily content for newsletters, social bots, and trivia agents.

Text embeddings API without an API key: up to 64 texts per call, 768-dimension embedding vectors computed on our own hardware. For semantic search, clustering, dedup, and RAG. Pay per call with USDC over x402; inputs never stored.

Descriptive statistics API: feed up to 100,000 numbers and get count, sum, mean, median, mode, sample standard deviation, variance, min/max/range, percentiles (p25/p50/p75/p90/p99), and IQR-flagged outliers. Deterministic and auditable — cheaper than burning reasoning tokens, zero arithmetic-hallucination risk, and the result can be cited. For data QA, monitoring, and analysis agents.

Chemical element API: atomic number, atomic mass, electron shells, electronegativity, and physical properties for any element. Local dataset, instant.

HTTP check API: probe any URL and get its status code, response time in milliseconds, server header, content type, and cache policy — an instant is-it-up heartbeat. For uptime monitors, dependency health checks, and pre-crawl validation. SSRF-guarded; scheduled agents welcome.

Claim-denial intelligence for a CARC code (e.g. CO-50, PR-204, CO-197). Returns plain-English meaning, category, whether it is appealable, the concrete next action, and how to prevent it. Unknown codes still get group-level (CO/PR/OA/PI) guidance. (AutomatedRCM agent: Dex)

Search the whole x402 economy and get a ranked shortlist of services that can do a job, within a budget. Merges Coinbase Bazaar and 402index into one index keyed by canonical resource URL, then answers the three questions a directory does not: CAN this be invoked (only about 5% publish a call spec, and that is a first-class field here, not something you infer from missing keys), is the price REAL (one live listing advertises ten billion dollars a call — implausible prices are excluded as bad data and reported, never silently rewritten), and is the demand real (total calls are trivially inflated by a merchant calling itself, so volume is credited only in proportion to distinct paying counterparties). Every result explains its own score, and the weights are returned so you can disagree with them. Lexical matching, no model: the same query against the same index ranks the same way.