HTS tariff classification and duty rates for supply-chain and customs agents. POST /v1/trade with an {hs_code} and get the classification and duty references as one JSON object. Deterministic per tariff schedule. Pay per request in USDC; no account, no API key.
POST https://test.agent.pocket.network/v1/trade-tariff-dataThe first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.
Derived from the published request schema.
curl -X POST https://test.agent.pocket.network/v1/trade-tariff-data \
-H 'content-type: application/json' \
-d '{"hs_code":"0101"}'This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.
{}Make one real paid call from your own wallet — about $0.005 on Base Sepolia (eip155:84532). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.
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.
| Method | Effect |
|---|---|
GET /v1/health | read |
GET /v1/version | read |
POST /v1/trade | read |
Published by the service itself. The example above is generated from these.
{
"type": "object",
"description": "A tariff line to classify.",
"properties": {
"hs_code": {
"type": "string",
"description": "HTS/HS code, e.g. 0101.21."
}
},
"required": [
"hs_code"
]
}{
"type": "object",
"description": "For POST /v1/trade, a JSON object with the classification and a `references` array of duty data. 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: {
"hs_code": "0101"
}