JE
Agent Service · x402 · early usage

Score up to 25 company or contact records against an ideal customer profile: 0-10 fit s…

Score up to 25 company or contact records against an ideal customer profile: 0-10 fit score, qualified / review / disqualified verdict, reason label. Calibrated on 240 labelled leads: 0.879 accuracy, and no qualified lead ever disqualified or vice versa. Catc…

by x402-production-0f93.up.railway.app · discovered, not yet claimed by its owner · updated 2026-09-25

30d calls1
30d payers1
MethodPOST
Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Score up to 25 company or contact records against an ideal customer profile: 0-10 fit score, qualified / review / disqualified verdict, reason label. Calibrated on 240 labelled leads: 0.879 accuracy, and no qualified lead ever disqualified or vice versa. Catches competitor name variants and subsidiaries of excluded accounts that string matching misses. Uncertainty widens the net: sparse records, unnamed contacts and low-confidence calls go to review, never to disqualified.

Tags: filter · classification · lead-scoring · data-cleaning · enrichment · bazaar

Call contract

Method
POST
Input
json
Output
json
Last paid call
2026-09-25
Input example from Bazaar metadata
{
  "buyerProfile": {
    "buyer_roles": [
      "VP Operations",
      "Plant Manager"
    ],
    "exclusions": {
      "competitors": [
        "Lenze"
      ],
      "existing_customers": []
    },
    "sells": "industrial motion-control retrofit kits",
    "target_industries": [
      "industrial automation",
      "packaging machinery"
    ],
    "target_regions": [
      "Germany",
      "Netherlands",
      "Nordics"
    ],
    "target_size": "50-1000 employees"
  },
  "leads": [
    {
      "company": "Acme Robotics GmbH",
      "contact": {
        "name": "A. Meyer",
        "title": "VP Operations"
      },
      "country": "Germany",
      "headcount": 180,
      "id": "l1",
      "industry": "industrial automation",
      "notes": "job board shows 3 open automation engineer roles"
    }
  ]
}
Output example
{
  "meta": {
    "bundle": "lead-qualifier",
    "bundle_version": "0.4.1",
    "elapsed_ms": 910,
    "failures": 0,
    "items": 1,
    "model_cost_usd": 0.000067
  },
  "results": [
    {
      "confidence": "medium",
      "id": "l1",
      "rationale": "jev@openrouter: qualified; reason buying_trigger; industry_match 0.93, geo_match 0.99, role_authority 0.95, buying_trigger 0.98, exclusion_hit 0.01",
      "reason": "buying_trigger",
      "rules_applied": [],
      "score": 9.05,
      "verdict": "qualified"
    }
  ]
}

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/38715.json for the price and payment options.
  3. Pay. Call GET https://x402-production-0f93.up.railway.app/v1/score-leads. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.1 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base
Demand
1 calls · 1 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.10x0FAa1f473CdF918d8437d0F746270b98f13b7307300s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x0FAa1f473CdF918d8437d0F746270b98f13b7307",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "100000",
    "amountUsd": 0.1,
    "maxTimeoutSeconds": 300
  }
]

Schemas

Output schema (JSON Schema)
{
  "properties": {
    "example": {
      "properties": {
        "meta": {
          "properties": {
            "bundle": {
              "type": "string"
            },
            "bundle_version": {
              "type": "string"
            },
            "elapsed_ms": {
              "type": "integer"
            },
            "engine": {
              "type": "string"
            },
            "failures": {
              "type": "integer"
            },
            "items": {
              "type": "integer"
            },
            "model_cost_usd": {
              "description": "What the call cost the server in model tokens. Published so you can see the markup you are paying.",
              "type": "number"
            },
            "questions_sha256": {
              "description": "Hash of the exact question wording used, so a result is reproducible.",
              "type": "string"
            }
          },
          "type": "object"
        },
        "results": {
          "items": {
            "properties": {
              "confidence": {
                "enum": [
                  "high",
                  "medium",
                  "low"
                ],
                "type": "string"
              },
              "error": {
                "description": "Present only when this one item could not be judged. Its verdict is then the safest rung, never a discard.",
                "type": "string"
              },
              "id": {
                "description": "The record's id field, or its index.",
                "type": "string"
              },
              "rationale": {
                "description": "The per-signal probabilities behind it.",
                "type": "string"
              },
              "reason": {
                "description": "A single label explaining the verdict.",
                "type": "string"
              },
              "rules_applied": {
                "description": "Which deterministic safety gates fired.",
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              "score": {
                "description": "0-10.",
                "type": "number"
              },
              "verdict": {
                "description": "One rung of the ladder for this operation.",
                "type": "string"
              }
            },
            "type": "object"
          },
          "type": "array"
        }
      },
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}
Example shape — generated from the schema, not a captured live response
{
  "example": {
    "meta": {
      "bundle": "string",
      "bundle_version": "string",
      "elapsed_ms": 0,
      "engine": "string",
      "failures": 0,
      "items": 0,
      "model_cost_usd": 0,
      "questions_sha256": "string"
    },
    "results": [
      {
        "confidence": "high",
        "error": "string",
        "id": "string",
        "rationale": "string",
        "reason": "string",
        "rules_applied": [
          "string"
        ],
        "score": 0,
        "verdict": "string"
      }
    ]
  },
  "type": "string"
}

Examples

curl
curl "https://x402-production-0f93.up.railway.app/v1/score-leads"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://x402-production-0f93.up.railway.app/v1/score-leads");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://x402-production-0f93.up.railway.app/v1/score-leads")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
x402-production-0f93.up.railway.app
Endpoint
https://x402-production-0f93.up.railway.app/v1/score-leads
Machine-readable
/resources/38715.json