export-screen-production.up.railway.app

Screen a company or person name against the official US Consolidated Screening List (BIS Entity List, Denied Persons, MEU, ITAR Debarred, Treasury SDN/SSI/CMIC; 11 lists). Returns no_match, possible_match, confirmed_match or unable_to_determine with confidence, sources and matches. Use when selling, shipping or transferring goods, software or technology to a foreign party and you must screen it against US export-control and restricted-party lists.

OtherLiveeip155:8453Exactvia cdp
Export-controlEntity-listBisRestricted-partyScreening
Calls · 30d
1
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 3 snapshots so far.
$1.02
Verified settled volume
45 settlements proven x402 by their on-chain EIP-3009 marker.
$0.020
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-10-16 19:29Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x922DAc4235B819F3C6778fB206333440b5A045B8

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.02USDC≈ $0.02 USD
on Base · exact scheme

Pay 0.02 USDC on Base to 0x922D…045B8. The signed payment is good for 5 minutes.

USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
20000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0x922DAc4235B819F3C6778fB206333440b5A045B8",
    "amount": "20000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "body": {
          "name": "Huawei Technologies"
        },
        "type": "http",
        "method": "POST",
        "bodyType": "json"
      },
      "output": {
        "type": "json",
        "example": {
          "legal": {
            "terms": "https://export-screen-production.up.railway.app/terms",
            "privacy": "https://export-screen-production.up.railway.app/privacy"
          },
          "query": {
            "name": "Huawei Technologies"
          },
          "status": "possible_match",
          "matches": [
            {
              "list": "EL",
              "type": "entity",
              "score": 1,
              "countries": [
                "CN"
              ],
              "exact_name": true,
              "list_title": "Entity List (EL) - Bureau of Industry and Security",
              "source_url": "https://www.bis.doc.gov/index.php/policy-guidance/lists-of-parties-of-concern/entity-list",
              "start_date": "2019-05-16",
              "matched_name": "Huawei Technologies Co., Ltd.",
              "country_match": null,
              "license_policy": "Presumption of denial",
              "match_strength": "name_only",
              "license_requirement": "For all items subject to the EAR...",
              "federal_register_notice": "84 FR 22963"
            }
          ],
          "sources": [
            {
              "id": "US_CSL",
              "name": "US Consolidated Screening List (trade.gov downloadable JSON)",
              "error": null,
              "stale": false,
              "available": true,
              "fetched_at": "2026-10-16T12:20:00.000Z",
              "last_updated": "2026-10-16T12:15:00Z",
              "dataset_version": "2026-10-16T12:15:00Z"
            }
          ],
          "use_when": "Use when selling, shipping or transferring goods, software or technology to a foreign party and you must screen it against US export-control and restricted-party lists.",
          "confidence": 0.9,
          "status_reason": "Name similarity to one or more list entries without a confirming identifier; verify identity against the source entry.",
          "total_matches": 3,
          "review_required": true,
          "coverage_limitations": "Covered: the 11 lists of the US CSL... No ownership/50% rule analysis..."
        }
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method",
            "bodyType",
            "body"
          ],
          "properties": {
            "body": {
              "required": [
                "name"
              ],
              "properties": {
                "name": {
                  "type": "string",
                  "description": "Company or person name to screen"
                },
                "limit": {
                  "type": "integer",
                  "description": "Max matches 1-25 (default 10)"
                },
                "lists": {
                  "type": "string",
                  "description": "Optional comma-separated list codes to restrict: EL,DPL,UVL,MEU,DTC,ISN,SDN,SSI,CMIC,PLC,MBS,CAP"
                },
                "country": {
                  "type": "string",
                  "description": "Optional country (ISO2 or name) to boost matches with that address country"
                },
                "min_score": {
                  "type": "number",
                  "description": "Minimum match score 0.7-1 (default 0.88)"
                }
              }
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "POST"
              ],
              "type": "string"
            },
            "bodyType": {
              "enum": [
                "json",
                "form-data",
                "text"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-10-16 19:29Z
Last indexed by Roundhouse
2026-10-17 19:40Z
Last enriched (probe, favicon, geo)
2026-10-16 17:16Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 402
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 3 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service export-screen-production.up.railway.app and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=export-screen-production.up.railway.app'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://export-screen-production.up.railway.app/v1/export/screen, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.