Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Pix QR Builder — connector documentation

  • MCP endpoint: https://br-pix-qr.connectorbay.com/mcp
  • REST API: POST https://br-pix-qr.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://br-pix-qr.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
  • Health: https://br-pix-qr.connectorbay.com/health · Tool schemas: https://br-pix-qr.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/br-pix-qr · agent@connectorbay.com

What Pix QR Builder is for

Pix QR Builder turns the public Pix BR Code rules into tools an agent can call. build_static_pix writes a static Pix payload from a Pix key, receiver name, city, optional amount and reference (txid), checks it again with a strict parser and returns a read-back (who is paid, where, how much) that the owner must confirm before the code is used. build_dynamic_pix_ref writes the payload of a dynamic code from the payment-location URL that the owner's payment provider issued. validate_pix_payload checks a pasted copia-e-cola string (structure, field lengths, fixed values, CRC16) and lists every error and warning; explain_pix_payload reads it field by field. compute_pix_crc, normalize_pix_text (accents and length limits, with a report of what changed), check_pix_key_format (format and check digits only, never a lookup) and pix_field_rules (every limit with its source) complete the set. Nothing is sent, paid or stored, and no Pix key is ever looked up. A wrong payload can send money to the wrong account, so every builder answer carries the read-back and says that the owner must confirm the receiver, city and amount. Built on the railqr library; the rules come from the Banco Central do Brasil manuals (BR Code v2.0.1 and Manual de Padroes para Iniciacao do Pix v2.10.0). Independent tool: not affiliated with or endorsed by Banco Central do Brasil.

Ask your assistant things like:

  • "Make me a Pix code for R$ 150.00 for order PED0042 to my CNPJ key, receiver Padaria Bom Pao in Sao Paulo, and let me confirm it"
  • "A customer sent me a Pix copia e cola: is it valid and who does it pay?"
  • "My company name has accents and is longer than the Pix limit: what goes into the code?"
  • "My bank gave me a Pix payment URL: build the QR payload for it"
  • "What are the field limits of a Pix code and which CRC does it use?"

What it does

  • build_static_pix: Build a static Pix BR Code (copia e cola) from a Pix key, receiver name, city, optional amount, txid and note, re-check it, and return a read-back for owner confirmation.
  • build_dynamic_pix_ref: Build the dynamic Pix BR Code from the payment-location URL issued by the owner's payment provider (no protocol prefix, at most 77 characters), with a read-back.
  • validate_pix_payload: Strictly check a Pix copia-e-cola payload: structure, lengths, fixed values, key format, CRC16; lists errors and warnings and a read-back of who it pays.
  • explain_pix_payload: Read a Pix payload field by field in plain language (kind, key type, receiver, amount, reference, recurrence) without judging its validity.
  • compute_pix_crc: CRC-16/CCITT-FALSE (polynomial 0x1021, initial value 0xFFFF) of a Pix payload body ending in 6304, or of any text in raw mode.
  • normalize_pix_text: Prepare a receiver name and city for a Pix code: remove accents, collapse spaces, optional upper case, cut to 25 and 15 characters, and report every change.
  • check_pix_key_format: Format and check-digit check of a Pix key (CPF, CNPJ including the alphanumeric format, +55 phone, e-mail, random key); never looks the key up.
  • pix_field_rules: The Pix BR Code field rules (lengths, allowed characters, fixed values, CRC) each with its source, verification level and manual section.

Data sources

Reference data from official sources (bcb.gov.br); every answer states its source, date and validity period.

What it is not

Pix QR Builder is independent; not affiliated with, endorsed by or operated by any government body, central bank, standards body or scheme operator. Names of rails, schemes and standards are used only to say what a tool works with. It is read-only: it never sends, pays, files or signs anything for you, and it never looks up private individuals.

Not advice. General information only, not legal, tax, accounting or payment advice. Pix QR Builder is an independent tool: it is not affiliated with, endorsed by or operated by any government body, central bank, standards body or scheme operator. Rates, thresholds and rules change; check the cited official source and confirm with a qualified professional before you rely on a result.

Built for: Brazil. Languages: English.

Tools

Look up & validate

validate_pix_payload — Strictly check a Pix copia-e-cola payload: structure, lengths, fixed values, key format and CRC16; lists errors and warnings and a read-back of who it pays. Use for "Is this Pix copia e cola string valid, and who does it pay?". Args: payload.

check_pix_key_format — Format and check-digit check of a Pix key (CPF, CNPJ including the alphanumeric format, +55 phone, e-mail, random key); never looks the key up. Use for "Is this a well-formed Pix key of the CNPJ type?". Args: pix_key.

Calculate

compute_pix_crc — CRC-16/CCITT-FALSE (polynomial 0x1021, initial value 0xFFFF) of a Pix payload body ending in 6304, or of any text in raw mode. Use for "What CRC16 goes at the end of this Pix payload?". Args: payload, raw.

Build & format

build_static_pix — Build a static Pix BR Code (copia e cola) from a Pix key, receiver name, city, optional amount, txid and note, re-check it with the strict parser and return a read-back for owner confirmation. Use for "Make me a Pix code for R$ 150.00 to my Pix key, receiver Padaria Bom Pao in Sao Paulo, reference PED0042". Args: pix_key, receiver_name, receiver_city, amount, txid, info, recurrence_url, truncate, include_svg.

build_dynamic_pix_ref — Build the dynamic Pix BR Code from the payment-location URL issued by the owner's payment provider (no protocol prefix, at most 77 characters), with a read-back. Use for "My bank gave me this Pix payment URL: turn it into a Pix QR code payload". Args: url, receiver_name, receiver_city, single_use, recurrence_url, truncate, include_svg.

Reference & guides

explain_pix_payload — Read a Pix payload field by field in plain language (kind, key type, receiver, amount, reference, recurrence) alongside its validity. Use for "Explain what every field of this Pix code means". Args: payload.

normalize_pix_text — Prepare a receiver name and city for a Pix code: remove accents, collapse spaces, optional upper case, cut to 25 and 15 characters, and report every change. Use for "My company name has accents and 31 characters: what goes into the Pix code?". Args: receiver_name, receiver_city, uppercase, truncate.

pix_field_rules — The Pix BR Code field rules (lengths, allowed characters, fixed values, CRC) each with its source, verification level and manual section. Use for "What are the size limits of the name, city and txid fields of a Pix code?". Args: field.

Conventions

  • Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
  • Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
  • Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/br-pix-qr/support