# Teppi Machine Delivery Evidence Record

> Teppi Machine Delivery Evidence Record is a paid API for AI agents from api.teppi.xyz, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-10).

Records and retrieves the actual response payload returned for a paid x402 agent call, serving as a verifiable delivery receipt for monitored endpoints and remote MCP servers.

## Facts

- Endpoint: POST https://api.teppi.xyz/v1/web/evidence?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/teppi-machine-delivery-evidence-record-069b3be5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JNh_VeqDkMCO7CbQvRtSC

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 teppi-machine-delivery-evidence-record-069b3be5 -d '<json body>'
```

Example prompt: Log the delivery evidence for the x402 call I just paid for — I need a record of what the endpoint actually returned so I can verify the response was delivered correctly.

## When to prefer this

Choose this endpoint when you need a tamper-evident, machine-readable log of what an x402 paid API call actually returned — especially for auditing, dispute resolution, or proving delivery in automated agent pipelines where payment was made and you need evidence of the response received. It is purpose-built for the x402 micropayment ecosystem and MCP server monitoring context.

## Known failure modes

- Missing or invalid call reference results in a rejection response
- Payment verification failure if the x402 transaction cannot be confirmed
- Duplicate submission of the same call evidence may return a conflict or deduplication response
- Malformed JSON body causes a 400-level error
- Endpoint or MCP server not found in the watched registry returns a not-found error

## How this service works

What came back for a paid agent call, written down: every x402 endpoint and remote MCP server we watch, and every call we paid for.

## Output

A JSON object confirming the delivery evidence record has been stored, containing details about the paid call response — including the endpoint called, the response payload received, and metadata identifying the transaction as a verified delivery record.

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/teppi-machine-delivery-evidence-record-069b3be5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.teppi.xyz](https://www.zero.xyz/host/api.teppi.xyz/llms.txt)