01 / Goal
Assess the security risk of a token.
Policy: evidence threshold, budget ceiling, and latency limit.
Procurement intelligence for agents
Your agent can pay. Spend402 decides what is worth buying.
Payment is an execution primitive. Spend402 is the decision layer: it selects evidence against a goal, budget, and stopping policy before an x402 payment is made.
No purchasing claim is made on this page. Protocol status is fetched separately and labeled when unavailable.
INPUT: GOAL + POLICY
OUTPUT: EVIDENCE + STOP REASON
OUTPUT: EVIDENCE + STOP REASON
Non-payment decision trace
The decision is legible before value moves.
A compact example of the information Spend402 evaluates. It is not a transaction record, price quote, or promise of outcome.
02 / Candidate quotes
Discover relevant payable capabilities.
Compare declared scope, price, constraints, and available evidence.
03 / Selected evidence
Choose only the next useful evidence source.
Selection explains its contribution to the active goal—not a generic ranking.
04 / Stop reason
Target met, budget boundary reached, or marginal value too low.
Stopping is a valid decision, including before any payment.
Architecture rail
A deliberate loop, not a buy button.
Each stage narrows uncertainty and produces context for the next one.
- 01
Plan
Turn a goal into evidence requirements, policies, and bounds.
- 02
Discover
Locate payable capabilities that could satisfy the requirement.
- 03
Validate
Check fit, terms, and available signals before procurement.
- 04
Procure
Authorize the selected x402 resource within the active policy.
- 05
Evaluate
Measure whether the returned evidence moved the task forward.
- 06
Stop
Record why continuing is not currently worth buying.
Methodology
Price is a signal. It is not the decision.
Spend402 does not claim a universal saving rate. The chosen method depends on the evidence a particular task needs.
Method 01
Cheapest-first
Routes to the lowest visible price. It can ignore relevance, complementarity, and the cost of insufficient evidence.
Method 02
Buy-all
Purchases every discovered option. It may produce redundancy and does not explain when enough evidence is already available.
Method 03 / Spend402
Decision layer
Plans required evidence, evaluates candidates in context, documents the selected contribution, and supplies a stop reason.
Protocol / public signal
Status without manufactured telemetry.
The landing reads the local public analytics endpoint defensively. A loading, empty, or unavailable state is shown when the schema or service cannot support a verified claim.
Checking public endpoint
Only a non-negative numeric procurement count is accepted from the endpoint.
Integration surface
Keep payment and decision in the same conversation.
HTTP / x402Procure through the API.
Send a goal, budget, quality target, and policy to POST /procure. The orchestration response can carry selections, receipts, evaluation context, and the stop reason.
MCP / agent toolsExpose decisions to an agent.
Use the project MCP surface to make procurement a tool call. The agent can request a scoped decision instead of treating every discovered paid resource as an automatic purchase.
Read MCP notes ↗Open implementation