Export Control Screening

compliance

Serving

Screen against the BIS Entity List and other restricted-party lists for trade compliance. POST /v1/export with a {name} and get matches and the lists checked as one JSON object. Deterministic per daily cache. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/export-control-screen
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

Derived from the published request schema.

curl -X POST https://agent.pocket.network/v1/export-control-screen \
  -H 'content-type: application/json' \
  -d '{"name":"string"}'

Example response

This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.

{}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Export Control Screening accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/export`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "A party to screen for export controls.",
  "properties": {
    "name": {
      "type": "string",
      "description": "Name to screen."
    }
  },
  "required": [
    "name"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/export, a JSON object with a `checked_lists` array and any restricted-party matches. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}

Request body used in the example: { "name": "string" }