Causal chain for Brazilian power risk: forecast rainfall over the Southeast/South (lead…
Causal chain for Brazilian power risk: forecast rainfall over the Southeast/South (leads reservoir levels by ~2-4 weeks) → stored hydro energy per subsystem and its 7-day slope, from the grid operator → likelihood of thermal dispatch and cost pressure. Brazil…
by api.brazilayer.com · discovered, not yet claimed by its owner · updated 2026-09-30
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Causal chain for Brazilian power risk: forecast rainfall over the Southeast/South (leads reservoir levels by ~2-4 weeks) → stored hydro energy per subsystem and its 7-day slope, from the grid operator → likelihood of thermal dispatch and cost pressure. Brazil runs on hydro: this is the upstream of industrial energy cost, and the rule and its limits travel in the response. Free sample, no payment: https://api.brazilayer.com/v1/cadeias/amostra
Tags: brazil · energy · power-grid · hydrology · causal-chain · bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-09-30
{}{
"cadeia": "energia_br",
"elos": [
{
"antecipa": "~2 a 4 semanas",
"posicao": "antecedente",
"sinal": "chuva prevista 7 dias",
"valor": 8.4
},
{
"posicao": "atual",
"sinal": "EAR SUDESTE",
"unidade": "%",
"valor": 63.4
}
],
"leitura": {
"estado": "pressao"
}
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/27308.jsonfor the price and payment options. - Pay. Call
GET https://api.brazilayer.com/v1/cadeias/energia_br. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.05 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 2 calls · 1 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.05 | 0x3Cc1D8ee1dfdFd326c19B0884B8dF4b24B623f0c | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x3Cc1D8ee1dfdFd326c19B0884B8dF4b24B623f0c",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "50000",
"amountUsd": 0.05,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://api.brazilayer.com/v1/cadeias/energia_br"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://api.brazilayer.com/v1/cadeias/energia_br");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://api.brazilayer.com/v1/cadeias/energia_br")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- api.brazilayer.com
- Endpoint
- https://api.brazilayer.com/v1/cadeias/energia_br
- Machine-readable
/resources/27308.json