Brazilian tools for agents: Pix, CEP, CNPJ, BCB rates + web capture and PDF. Pay per call.
The Brazilian toolkit for AI agents — plus the web and document work agents can't do inside a sandbox.
Ask your agent to generate a Pix payment code, resolve a CEP to a full address, or pull a company's record from the CNPJ registry. Point it at a JavaScript-heavy page and get clean Markdown, a screenshot or a PDF back.
A CNPJ lookup costs $0.01 — billed per call, with no monthly plan, no contract and no minimum, which is unusual for Brazilian data APIs.
Each tool maps to an HTTP endpoint of the same service:
| Tool | Endpoint |
|---|---|
pix_brcode | POST /pix/brcode |
cep_lookup | POST /cep |
cnpj_lookup | POST /cnpj |
empresa_profile | POST /empresa |
url_to_markdown | POST /url-to-markdown |
screenshot_url | POST /screenshot |
url_to_pdf | POST /url-to-pdf |
extract | POST /extract |
compress_pdf | POST /compress-pdf |
Brazilian sources, handled properly. CEP lookups hit BrasilAPI first and fall back to ViaCEP automatically, so a single upstream outage doesn't break your agent. Both sources come back through one normalized, English-keyed shape — your prompt never has to know which one answered.
Pix codes built to spec, locally. The BR Code follows the Central Bank's EMV layout, CRC16 and all, generated on our side with no third-party payment provider in the path. The key you send is used to build the code and is not stored.
Privacy taken seriously. CNPJ responses carry the company record — legal name, trade name, status, main activity, address — with personal fields left out by design.
Rendering that doesn't become an attack surface. The web tools run real Chromium, so JavaScript pages resolve, and they refuse private and internal addresses (SSRF guard) before a page is ever loaded.
Nothing to install for the hard parts. Ghostscript and a headless browser are the kind of dependency an agent sandbox doesn't have and can't install. That is exactly what this is for — anything an agent already does well on its own (parsing a CSV, reading a spreadsheet) is not sold here.
Works with Claude Desktop, Claude Code, Cursor, Windsurf, Cline and any MCP client.
{
"mcpServers": {
"miniframe-tools": {
"command": "npx",
"args": ["-y", "miniframe-tools-mcp"],
"env": {
"EVM_PRIVATE_KEY": "0xyour_private_key"
}
}
}
}
Restart the client and the seven tools appear. Then just ask:
"Generate a Pix code for R$ 50 to key
abc@example.com, name Maria Silva, city Recife""What's the address for CEP 01310-100?"
"Look up CNPJ 00.000.000/0001-91 and tell me if the company is active"
"Turn https://example.com into Markdown so I can summarise it"
No MCP needed — every tool is a normal endpoint:
curl -i -X POST https://tools.miniframe.com.br/cep \
-H "Content-Type: application/json" \
-d '{"cep":"01310100"}'
Calls are billed per request in USDC on Base, using the
x402 protocol: the endpoint answers 402 with the price, your
client signs the payment and repeats the request. Most agent runtimes handle this
for you.
For MCP, set EVM_PRIVATE_KEY to a wallet funded with a few dollars of USDC — use a
dedicated low-balance wallet, never your main one. The key stays on your machine and
signs locally; it is never sent to the API.
| Variable | Required | Default |
|---|---|---|
EVM_PRIVATE_KEY | yes | — |
MINIFRAME_API_URL | no | https://tools.miniframe.com.br |
Over plain HTTP, wrap your client with any x402 library — see
examples/ for a runnable Node script.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y miniframe-tools-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-edsonvmendes-miniframe-tools": {
"command": "npx",
"args": [
"-y",
"miniframe-tools-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceminiframe-tools-mcpnpmio.github.edsonvmendes/miniframe-tools works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.