JE
Identity & Enrichment · x402 · early usage

Filter up to 25 records against up to 10 yes/no criteria you supply

Filter up to 25 records against up to 10 yes/no criteria you supply. Each record comes back with keep / review / drop, a reason naming the criterion it failed, a 0-10 score and the per-criterion probabilities. Never drops a record it could not read or could n…

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

30d calls3
30d payers3
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

Filter up to 25 records against up to 10 yes/no criteria you supply. Each record comes back with keep / review / drop, a reason naming the criterion it failed, a 0-10 score and the per-criterion probabilities. Never drops a record it could not read or could not judge: those come back as review or keep, flagged. Built on a decision model rather than a chat model, so it is a flat per-call price with no token accounting on your side.

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

Call contract

Method
POST
Input
json
Output
json
Last paid call
2026-10-02
Input example from Bazaar metadata
{
  "criteria": [
    {
      "key": "in_europe",
      "question": "The company operates in Europe."
    },
    {
      "key": "makes_things",
      "question": "This is a company that manufactures or automates physical production, not a service business."
    }
  ],
  "mode": "all",
  "records": [
    {
      "company": "Nordfjord Packaging AS",
      "contact": "S. Halvorsen",
      "country": "Norway",
      "id": "1"
    },
    {
      "company": "Bright Ideas Consultancy",
      "contact": "",
      "country": "UK",
      "id": "2"
    }
  ]
}
Output example
{
  "meta": {
    "bundle": "dataset-filter",
    "bundle_version": "0.1.0",
    "elapsed_ms": 640,
    "failures": 0,
    "items": 2,
    "model_cost_usd": 0.00012
  },
  "results": [
    {
      "confidence": "high",
      "id": "1",
      "rationale": "jev@openrouter: keep; reason all_criteria_met; in_europe 0.99, makes_things 0.97",
      "reason": "all_criteria_met",
      "rules_applied": [],
      "score": 9.81,
      "verdict": "keep"
    },
    {
      "confidence": "high",
      "id": "2",
      "rationale": "jev@openrouter: drop; reason failed_makes_things; in_europe 0.98, makes_things 0.03",
      "reason": "failed_makes_things",
      "rules_applied": [
        "require_makes_things"
      ],
      "score": 4.9,
      "verdict": "drop"
    }
  ]
}

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/38714.json for the price and payment options.
  3. Pay. Call GET https://x402-production-0f93.up.railway.app/v1/filter. 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.01 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base
Demand
3 calls · 3 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.010x0FAa1f473CdF918d8437d0F746270b98f13b7307300s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x0FAa1f473CdF918d8437d0F746270b98f13b7307",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "10000",
    "amountUsd": 0.01,
    "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/filter"
# -> 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/filter");
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/filter")
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/filter
Machine-readable
/resources/38714.json