# x402 Buyer Intent Scoring

> x402 Buyer Intent Scoring is a paid API for AI agents from x402-seller.558686.xyz, paid per call via x402, $0.007/call, status unknown (last checked 2026-09-15).

Scores and segments a list of potential buyers by their intent, urgency, budget, and matched routes to prioritize seller outreach in x402 API marketplaces.

## Facts

- Endpoint: POST https://x402-seller.558686.xyz/v1/tools/x402-buyer-intent-scoring
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-buyer-intent-scoring-c34d4e39
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kRN6mu9C2afyeHyu4p4HF

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-buyer-intent-scoring-c34d4e39 -d '<json body>'
```

Example prompt: Score these two x402 buyers for me: 'agent-builder' has high urgency, needs an x402 receipt gate, budget of $0.05, requires an openapi proof, and matched the x402-quote-inspector route; 'api-consumer' has medium urgency, needs rate-limited access, budget of $0.20, requires a jwt proof, and matched x402-directory-submission — tell me which one to prioritize and what action to take next.

## When to prefer this

Use this endpoint when you are an x402 API seller wanting to prioritize outreach among multiple potential buyers by scoring their intent, urgency, and budget fit. Prefer this over generic CRM scoring tools when your buyers are specifically x402 protocol participants with matched routes and proof requirements.

## Known failure modes

- Missing required buyer fields (id, useCase, budgetUsd, urgency, proofNeeds, matchedRoutes) cause validation errors
- Empty buyers array returns no scored results
- Invalid urgency or proofNeeds values may produce unexpected segment assignments
- Payment failure (402) if x402 USDC payment is not completed before the call
- Malformed JSON body returns a 400-level error

## How this service works

Operational x402 seller tools for market benchmark, buyer shortlist, seller action plan, directory rank tracker, quote inspector, competitor listing audit, directory submission kit, price band advice, and buyer intent scoring workflows.

## Output

Returns a JSON object containing buyer segments, the total count of scored buyers, and a 'nextBestAction' recommendation string guiding the seller on which buyer to engage and how — computed deterministically from the input buyer profiles.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "x402-buyer-intent-scoring",
  "input": {
   "buyers": [
    {
     "id": "agent-builder",
     "urgency": "high",
     "useCase": "needs x402 receipt gate",
     "budgetUsd": 0.05,
     "proofNeeds": [
      "openapi"
     ],
     "matchedRoutes": [
      "x402-quote-inspector"
     ]
    }
   ]
  },
  "route": "/v1/tools/x402-buyer-intent-scoring",
  "result": {
   "segments": "segments_example",
   "scoredBuyers": 1,
   "nextBestAction": "nextBestAction_example"
  },
  "project": "x402-seller-growth-tools",
  "deterministic": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-buyer-intent-scoring-c34d4e39/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-seller.558686.xyz](https://www.zero.xyz/host/x402-seller.558686.xyz/llms.txt)