# Vibes-Coded Action Receipt API

> Vibes-Coded Action Receipt API is a paid API for AI agents from vibes-coded.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-13).

Issues a cryptographically signed action receipt after a paid agent tool call, returning a verifiable proof-of-execution artifact with HMAC and digest.

## Facts

- Endpoint: POST https://vibes-coded.com/api/v1/outcomes/action-receipt
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibes-coded-action-receipt-api-faa5ac77
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mTsd48VMeTSpM_pruGbbV

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 vibes-coded-action-receipt-api-faa5ac77 -d '<json body>'
```

Example prompt: After completing that paid skill invocation, can you mint me an action receipt from Vibes-Coded for the 'listing.optimize' action under my agent ID 'agent-abc-001' so I have a signed, verifiable proof with an HMAC that I can audit later?

## When to prefer this

Choose this endpoint when you need a cryptographically verifiable, nonce-backed proof that a specific AI agent action was executed — especially in audit, compliance, or multi-agent accountability scenarios. Prefer it over simple logging when HMAC verification and a public-key-backed receipt are required. Ideal for pay-per-call agent workflows where financial accountability and action provenance matter.

## Known failure modes

- HTTP 402 returned if USDC payment is not included or insufficient — agent must attach x402 payment header
- Invalid or missing agent_id returns an error response
- Unknown or unsupported action name may result in a rejected receipt
- Network timeout or upstream failure may prevent receipt issuance
- Malformed payload digest causes validation rejection

## How this service works

Pay-per-call JSON for AI agents: skill search, listing optimization, install plans, productization, and artifact risk scoring. HTTP 402 → USDC. Full skill marketplace on-site.

## Output

A JSON object containing: a boolean 'ok' status, a unique nonce for the receipt, the action name, agent ID, resource name, receipt type and profile, a SHA-256 payload digest, an HMAC validity hint, a public key URL for signature verification, and a verify endpoint URL for independent confirmation.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "note": "Shape of a paid mint — unpaid sample also at GET …/action-receipt/sample",
  "nonce": "sample-receipt-v1-raw0001",
  "quote": "public-sample",
  "action": "sample.ping",
  "verify": "https://vibes-coded.com/api/v1/outcomes/action-receipt/verify",
  "profile": "action-receipt-v1-rt",
  "agent_id": "vibes-sample",
  "resource": "action-receipt",
  "public_key": "https://vibes-coded.com/api/v1/outcomes/action-receipt/public-key",
  "hmac_ok_hint": true,
  "receipt_type": "raw",
  "payload_digest": "sha256:sample"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibes-coded-action-receipt-api-faa5ac77/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vibes-coded.com](https://www.zero.xyz/host/vibes-coded.com/llms.txt)