# Synthex Forge Evidence Ingest

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

Records a signed, tamper-evident evidence artifact for a given action, actor, and optional policy reference into an Ed25519+SHA-256 attested audit log.

## Facts

- Endpoint: POST https://x402.synthexforge.com/v1/evidence/ingest?utm_source=zero.xyz
- Price: $0.2/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-evidence-ingest-cc839af5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XuHIu7lmCBNxnui6mLmeJ

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-evidence-ingest-cc839af5 -d '<json body>'
```

Example prompt: Record a signed evidence entry that wallet did:key:z6Mk... reviewed and approved proposal #42 under policy ref 'gov-policy-2024-01', with action hash 'a3f9c2...', timestamped now.

## When to prefer this

Choose this endpoint when you need cryptographically signed, tamper-evident audit records anchored to a DID-identified actor and an optional policy reference, with Ed25519+SHA-256 attestation. Prefer it over generic logging services when compliance, governance, or verifiable audit trails are required, especially in decentralized or blockchain-adjacent workflows using USDC micropayments on Base.

## Known failure modes

- Missing required 'action' or 'actor_did' fields returns a 400 validation error
- Invalid DID format for actor_did may cause rejection
- Malformed action_hash (non-hex or wrong length) may trigger a 400 error
- Payment not provided or invalid x402 USDC payment results in HTTP 402 payment-required response
- Network or chain issues on Base mainnet may delay payment confirmation and return a 402 or 503
- Duplicate submissions with same action_hash may return an idempotency conflict or silently succeed depending on server policy

## 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

Returns a JSON object with {ok: true} confirming the evidence artifact was successfully ingested and cryptographically attested. The signed artifact is stored server-side with Ed25519 signature and SHA-256 hash for future verification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "action": {
   "type": "string",
   "description": "Human-readable description of the action."
  },
  "metadata": {
   "type": "object"
  },
  "actor_did": {
   "type": "string",
   "description": "The actor who did the action (DID / wallet / service key)."
  },
  "timestamp": {
   "type": [
    "string",
    "number"
   ],
   "description": "Optional caller-claimed event timestamp (epoch or ISO)."
  },
  "policy_ref": {
   "type": "string"
  },
  "action_hash": {
   "type": "string",
   "description": "Optional hex SHA-256 of the action; if omitted, derived deterministically."
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthex-forge-evidence-ingest-cc839af5/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)