# Synthex Forge SEC Extract

> Synthex Forge SEC Extract is a paid API for AI agents from x402.synthexforge.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-23).

Extracts security-related data for a given ticker symbol, returning a signed attestation artifact via a paid x402 endpoint.

## Facts

- Endpoint: POST https://x402.synthexforge.com/v1/sec-extract?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthex-forge-sec-extract-594225e9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DZ1BUtaiC3ZHfByNu95h0

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 synthex-forge-sec-extract-594225e9 -d '<json body>'
```

Example prompt: Can you extract the security data for ticker AAPL and give me a signed attestation result?

## When to prefer this

Use this endpoint when you need a cryptographically signed, attested security data extract for a specific stock ticker and require the artifact to carry Ed25519 + SHA-256 provenance for compliance, governance, or audit purposes. Prefer it over generic financial data APIs when tamper-evident attestation is a hard requirement.

## Known failure modes

- HTTP 402 returned if x402 payment is not attached or is invalid
- Invalid or unrecognized ticker symbol returns an error
- Malformed request body missing the `ticker` field causes a 400 error
- Network or upstream data source unavailability causes a 503
- Payment settlement failure on Base mainnet blocks the response

## How this service works

Synthex Forge x402 Receive: 41 paid verification, attestation and governance endpoints (Ed25519 + SHA-256 signed artifacts) plus free verify/public-key/standard sibling routes. Paid routes answer HTTP 402 with an x402 v2 `payment-required` envelope (atomic USDC on Base mainnet, chain ID 8453). Free routes are declared with `security: []` per the x402scan discovery spec.

## Output

A JSON object with an `ok` boolean field indicating success, along with a cryptographically signed (Ed25519 + SHA-256) attestation artifact containing extracted security data for the requested ticker symbol.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ticker": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthex-forge-sec-extract-594225e9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.synthexforge.com](https://www.zero.xyz/host/x402.synthexforge.com/llms.txt)