# Pocket Network Export Control Screening

> Pocket Network Export Control Screening is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Screens a named entity against the BIS Entity List and other export-control restricted-party lists, returning matches and lists checked as a single JSON object.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/export-control-screen?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-export-control-screening-751abe56
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__u2lmxaPB9CiY6tTNzKGb

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 pocket-network-export-control-screening-751abe56 -d '<json body>'
```

Example prompt: Can you screen 'Huawei Technologies Co. Ltd' against the BIS Entity List and any other export control restricted-party lists to see if there are any matches?

## When to prefer this

Use this endpoint when you need to screen specifically against the BIS Entity List and export control restricted-party lists for trade compliance purposes. If you need OFAC SDN or SEC enforcement screening instead, use the sibling watchlist endpoint on agent.pocket.network. This endpoint is ideal for supply-chain, procurement, and export licensing workflows that require BIS compliance checks without requiring an account or API key — pay-per-request in USDC.

## Known failure modes

- Missing or empty 'name' field returns a validation error
- Names with ambiguous spelling may produce false negatives or false positives due to fuzzy/exact matching logic
- Daily cache may not reflect intra-day list updates
- Payment failure (insufficient USDC) results in a 402 rejection before screening occurs
- Very short or generic names may match too many entries or none

## How this service works

Pay-per-call access to Pocket Network services. No account, no API key.

## Output

A JSON object containing the matched entries found (if any) across all checked lists, along with the names of the lists that were screened (e.g. BIS Entity List). Results are deterministic within a daily cache window, so repeated calls with the same name on the same day return the same result.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "Name to screen."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "portal": {
   "serviceId": "export-control-screen",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-export-control-screening-751abe56/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)