# agentfeeds.jp Sanctions Address Status As-Of Date Lookup

> agentfeeds.jp Sanctions Address Status As-Of Date Lookup is a paid API for AI agents from api.agentfeeds.jp, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Returns the historical sanctions list status (JP MOF and OFAC) for a crypto/entity address as of a specified past date, using a recorded list-change log with provenance labels per jurisdiction.

## Facts

- Endpoint: GET https://api.agentfeeds.jp/v1/reg/sanctions/as_of
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentfeeds-jp-sanctions-address-status-as-of-date-lookup-df2099db
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XIsQ5reW5mrYg6SA6MWBh

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 agentfeeds-jp-sanctions-address-status-as-of-date-lookup-df2099db
```

Example prompt: Can you check whether the address 0x1234abcd5678ef901234abcd5678ef901234abcd was on the JP MOF or OFAC sanctions list as of January 15, 2024, and tell me how that status was derived — whether it was directly observed in the list or inferred?

## When to prefer this

Use this endpoint when you need the historical sanctions status of an address at a specific past date — not just its current status. It is the right choice for compliance audits, retroactive screening, or investigating whether an address was sanctioned at the time of a past transaction. Prefer it over the real-time screening endpoint when the temporal context of the query is a past date. Note that it draws on the same underlying JP MOF/OFAC data as the sibling diff endpoints, so it adds no new data source but provides convenient date-scoped access with provenance labels.

## Known failure modes

- Missing required 'address' query parameter returns an error
- Address string too short or too long (outside 20-100 alphanumeric chars) returns validation error
- Invalid or unparseable ISO date in 'as_of' parameter returns an error
- Date too far in the past for which no list-change log data exists returns 'insufficient_data' labels
- Address has no recorded history in any jurisdiction returns all-'insufficient_data' response
- Service unavailable or payment not processed results in 402 or 5xx error

## How this service works

Date-scoped variant of our JP MOF / OFAC address list lookup: returns list status for a chosen date instead of only today, using our own previously-recorded list-change log (same underlying data as sanctions.jp.diff / sanctions.ofac.diff -- no new data source). Each jurisdiction result includes a label describing how the value was derived: observed, inferred, assumed_unchanged, or insufficient_data. Factual reference data only; not legal or investment advice.

## Output

A per-jurisdiction breakdown (JP MOF and OFAC) of the address's sanctions list status as of the requested date, each result labeled with how the value was derived: 'observed' (directly seen in list data), 'inferred' (derived from surrounding change events), 'assumed_unchanged' (no change events found, last known state carried forward), or 'insufficient_data' (not enough history to determine).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "as_of": {
       "type": "string",
       "description": "optional ISO date/time to check status as of, default now"
      },
      "address": {
       "type": "string",
       "description": "20-100 alphanumeric chars"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentfeeds-jp-sanctions-address-status-as-of-date-lookup-df2099db/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentfeeds.jp](https://www.zero.xyz/host/api.agentfeeds.jp/llms.txt)