# FractalAI Stablecoin Receipt

> FractalAI Stablecoin Receipt is a paid API for AI agents from fractalai.net.co, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Generates a post-quantum ML-DSA-65 cryptographic receipt for an on-chain Latin American stablecoin transfer

## Facts

- Endpoint: POST https://fractalai.net.co/api/x402/stablecoin-receipt?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fractalai-stablecoin-receipt-c09420e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__u6Mh3pY31vNSsKMyM4AH

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 fractalai-stablecoin-receipt-c09420e6 -d '<json body>'
```

Example prompt: I just sent a USDC stablecoin transfer on a LatAm blockchain network — can you get me a post-quantum ML-DSA-65 receipt sealing the transaction details so I have a verifiable cryptographic proof of the payment?

## When to prefer this

Choose this endpoint when you need a post-quantum cryptographic receipt specifically for a Latin American stablecoin transfer and require ML-DSA-65 (Dilithium-3) quantum-resistant signatures. Prefer it over generic notary or provenance endpoints when the subject is explicitly an on-chain LatAm stablecoin payment and you need a self-contained, verifiable transfer receipt rather than a general-purpose document seal.

## Known failure modes

- Missing required fields in the transfer body result in a 400 validation error
- Invalid HTTP method (must be POST, PUT, or PATCH) causes rejection
- Malformed or non-JSON body when bodyType is set to json returns a parse error
- Payment of $0.01 USDC not included or rejected causes a 402 Payment Required response
- Transfer data that cannot be canonicalized or hashed results in signing failure

## How this service works

Post-quantum ML-DSA-65 receipt for an on-chain LatAm stablecoin transfer

## Output

A post-quantum ML-DSA-65 (Dilithium-3 / NIST FIPS 204) cryptographic receipt attesting the details of the submitted on-chain LatAm stablecoin transfer, providing a tamper-evident, quantum-resistant proof of the transaction that can be independently verified.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fractalai-stablecoin-receipt-c09420e6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fractalai.net.co](https://www.zero.xyz/host/fractalai.net.co/llms.txt)