Get started

Quickstart

Choose MCP when an agent should decide which data to retrieve. Choose REST when your application controls the request flow.

01 · MCP

Connect your agent

claude mcp add --transport http bolsix https://mcp.bolsix.io/

Try: “Compare VALE3 and PETR4 on P/E, EV/EBITDA, and ROE.”

MCP setup details →

02 · REST

Call the API

Try it without a key: PETR4, VALE3, ITUB4, HGLG11 and BOVA11 answer on the quote, prices, fundamentals and dividends endpoints, 100 requests a day per IP.

curl "https://api.bolsix.io/v1/stocks/quote?symbols=PETR4,VALE3"

For every ticker and endpoint, create a free API key in the dashboard (1,000 requests a day) and send it as a Bearer token from your backend.

curl "https://api.bolsix.io/v1/stocks/quote?symbols=MGLU3,WEGE3" \
  -H "Authorization: Bearer bx_live_..."

REST conventions →

Read the response

Successful REST responses use the same top-level shape. Endpoint-specific context and provenance live in meta.

JSON

{
  "data": [{ "symbol": "PETR4", "price": 38.42 }],
  "meta": {
    "exchange": "BVMF",
    "currency": "BRL",
    "data_source": "b3",
    "took_ms": 1
  },
  "status": "ok"
}

Keep credentials server-side

Never embed a Bolsix API key in browser JavaScript, a mobile binary, or a public repository. Proxy requests through your backend and use separate keys per environment.