# SYNTHORA Endpoint Trust

> SYNTHORA Endpoint Trust is a paid API for AI agents from api.hergertsynthora.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-13).

Performs a pre-payment trust verification of any x402 endpoint — checking 402 correctness, valid payment fields, bazaar extensions, agent-card publication, and latency based on observed behavior.

## Facts

- Endpoint: POST https://api.hergertsynthora.com/v1/endpoint-trust
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthora-endpoint-trust-b8475ca5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mpfdRTtSHOgaNMk7sTQtV

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 synthora-endpoint-trust-b8475ca5 -d '<json body>'
```

Example prompt: Before I pay that x402 endpoint at https://api.example.com/v1/some-service, run a SYNTHORA trust check on it — I need to know if the 402 headers are correct, the payTo address is valid, it has a published agent card, and what the latency looks like.

## When to prefer this

Choose this endpoint when an AI agent or autonomous system is about to make a payment to an x402-gated API and needs an objective, observed-behavior trust verdict rather than relying on self-declared metadata. Especially valuable before first-time payments to unknown providers discovered on bazaar or agentic.market, when building payment guardrails into agent workflows, or when auditing your own x402 endpoints for spec compliance.

## Known failure modes

- Target endpoint is unreachable or times out — trust verdict returns as unresolvable
- Target endpoint does not respond with a 402 status — check fails or returns non-compliant result
- Malformed input URL causes request rejection
- Target endpoint blocks automated probes — partial or incomplete trust data returned
- SYNTHORA itself returns 402 if caller has not paid the $0.005 USDC fee

## How this service works

SYNTHORA endpoint-trust: trust verdict for any x402 endpoint before paying it — 402 correctness, valid accepts/payTo, bazaar extensions, agent-card published, latency. Observed behavior, not declarations. The pre-payment check for buying agents. $0.005 USDC x402 Base.

## Output

Returns an observed-behavior trust verdict for the given x402 endpoint, including: whether the 402 response is correctly formed, validity of the accepts and payTo payment fields, compliance with bazaar protocol extensions, whether an agent card is published, and measured latency — all based on live probing rather than self-declared metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "description": "SYNTHORA endpoint-trust: trust verdict for any x402 endpoint before paying it — 402 correctness, valid accepts/payTo, bazaar extensions, agent-card published, latency. Observed behavior, not declarati"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthora-endpoint-trust-b8475ca5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.hergertsynthora.com](https://www.zero.xyz/host/api.hergertsynthora.com/llms.txt)