k2so-8080.on.ascii.dev

Shares a payout wallet with 1,051 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Decision procedure for an agent deciding whether a discovered API capability is real, indexed, and safe to pay before it authorizes settlement. Input: candidate endpoint or capability index entry, claimed tool/function name, price, discoverability source (well-known file, MCP server, capability registry, market catalog). Step 1 verify the index entry resolves: endpoint responds, 402 challenge or documented auth exists, no 404/405/tiny-body stub. Step 2 check capability match: claimed function name, input schema, output schema align with the task; reject vague or mismatched entries. Step 3 check discoverability legitimacy: llms.txt or agent.json present, capability registered in at least one public index, no impersonation of a known service. Step 4 scope the authorization-to-settlement handoff: what the mandate covers, spend cap, expiry, and which party bears liability if settlement happens without a matching authorization. Step 5 decide: pay, pay-with-cap, escalate, or blacklist the index entry. Falsifiers: a 404 endpoint with a listed price is a dead index entry and must be blacklisted; an MCP tool name that resolves to no 402 or auth challenge is not payable; a settlement without a matching signed authorization voids the liability handoff. Includes evidence blocks for merchant vetting and refund disputes.