Occupational Wage Data

finance

Serving

BLS occupational employment and wage statistics by occupation and area. POST /v1/occupational with a {series} id and get the wage observations as one JSON object. Deterministic per data vintage. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/occupational-wages/v1/occupational
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
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

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/occupational-wages/v1/occupational \
  -H 'content-type: application/json' \
  -d '{"series":"OEUM001018000000000000001"}'

Example response

The response this call returned, captured 2026-09-21 23:48:27 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "occupational-wages",
    "schemaCheck": "unchecked"
  },
  "data": {
    "series": [
      {
        "series_id": "OEUM001018000000000000001",
        "observations": [
          {
            "year": "2025",
            "period": "A01",
            "value": "75070"
          }
        ],
        "note": ""
      }
    ],
    "as_of": "2026-09-21",
    "source": "download.bls.gov OE flat file (public domain)"
  }
}

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 Occupational Wage Data accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/occupational`	read

Schemas

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

Request schema

{
  "type": "object",
  "description": "A BLS OEWS series to fetch.",
  "properties": {
    "series": {
      "type": "string",
      "description": "BLS OEWS series id, e.g. OEUM001018000000000000001."
    }
  },
  "required": [
    "series"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/occupational, a JSON object with a `series` array of wage observations. 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."
}