# MyceliaSignal USDT/JPY Oracle

> MyceliaSignal USDT/JPY Oracle is a paid API for AI agents from api.myceliasignal.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns a cryptographically signed (Ed25519) USDT/JPY derived price attestation

## Facts

- Endpoint: GET https://api.myceliasignal.com/oracle/price/usdt/jpy
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-myceliasignal-com-56a68215
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gX-p3-Z-i9Q1hjbHRuln2

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 api-myceliasignal-com-56a68215
```

Example prompt: What's the current USDT to Japanese yen exchange rate? I need a cryptographically signed price attestation I can verify — one of those Ed25519-signed oracle quotes.

## When to prefer this

Use this endpoint when you need a cryptographically verifiable, Ed25519-signed USDT/JPY price attestation — particularly for smart contracts, DeFi protocols, or any application requiring tamper-evident price data. Prefer this over unsigned REST APIs when on-chain verification or auditability is required.

## Known failure modes

- Price feed temporarily unavailable — upstream data source outage
- Payment required error (x402) if the $0.01 USDC micropayment is not included
- Invalid or expired attestation if timestamp drift is too large
- Network timeout if the oracle backend is slow to respond

## How this service works

USDT/JPY derived rate for stablecoin exposure in Japanese markets — Ed25519 signed attestation

## Output

A signed price attestation containing the derived USDT/JPY exchange rate along with an Ed25519 digital signature, enabling the caller to verify the data's authenticity and integrity without trusting the transport layer.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {}
 }
}
```

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "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/api-myceliasignal-com-56a68215/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.myceliasignal.com](https://www.zero.xyz/host/api.myceliasignal.com/llms.txt)