# Public Security.txt Disclosure Policy Lookup

> Public Security.txt Disclosure Policy Lookup is a paid API for AI agents from api.the402.ai, paid per call via x402, $0.053/call, status down (last checked 2026-09-15).

Fetches a website's security.txt disclosure policy including contacts, expiry dates, and cryptographic hashes via a paid micropayment API call.

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_c49173e39c024738/purchase
- Price: $0.053/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/public-security-txt-disclosure-policy-lookup-3fa54ada
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jUSBIhtjkcpU0RcLuP1c3

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 public-security-txt-disclosure-policy-lookup-3fa54ada -d '<json body>'
```

Example prompt: Can you look up the security.txt disclosure policy for example.com — I need the responsible disclosure contacts, expiry date, and any cryptographic hashes listed there?

## When to prefer this

Use this endpoint when you need to programmatically retrieve a domain's responsible disclosure policy, security contacts, or verify security.txt hashes without manually fetching and parsing the file yourself. Prefer it over manual HTTP fetch when you want structured output and audit trail via job tracking.

## Known failure modes

- Target domain has no security.txt file — job returns empty or error status
- Malformed or non-standard security.txt causes parsing failure
- Payment of 0.053 USDC not accepted, returning HTTP 402
- Invalid service ID causes 404 or rejection
- Job hangs if target domain is unreachable, requiring status polling to detect timeout

## How this service works

Purchase: Public Security.txt Disclosure Policy — Contacts, Expiry & Hashes

## Output

Returns a job_id, status string, and thread_id representing the initiated lookup job. The agent can use the job_id to poll for the full security.txt contents including disclosure contacts, policy expiry, and cryptographic hashes once processing completes.

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "job_id": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "thread_id": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/public-security-txt-disclosure-policy-lookup-3fa54ada/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.the402.ai](https://www.zero.xyz/host/api.the402.ai/llms.txt)
