Integration

OpenPix integration

Brazilian Pix payments through the OpenPix (Woovi) API: create dynamic Pix charges and read their EMV payload and QR code image, manage the customers those charges belong to, open static Pix QR codes for a fixed key, list the Pix transactions credited to the account, issue full or partial refunds on a charge or on a raw transaction, and register webhooks so an incoming payment can start a workflow. Amounts are always integers in cents and every object can be addressed by your own correlationID instead of the OpenPix identifier.

Connect OpenPix How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in OpenPix.Built from the 18 OpenPix tools below, on the connection you add once.

Common OpenPix use cases

polling a charge until it is paid
auditing which printed QR codes exist
correcting the email of a registered payer
charging a customer over Pix from a workflow
identifying who actually sent a received Pix
refunding a customer after a cancelled order
exporting the registered payers of an account
reconciling the charges created over a period
giving a payer more time before a charge expires
reconciling received Pix payments against charges

What you can do with OpenPix

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Charge, 5 operations

create_chargeCreate chargePOSTOpens a new Pix charge for an amount in cents and returns everything needed to collect it.
delete_chargeDelete chargeDELETERemoves a charge and returns a short confirmation carrying its identifier.
get_chargeGet chargeGETReturns the current state of a single charge, including its Pix payload.
list_chargesList chargesGETReturns the charges of the account together with paging counters.
update_charge_expirationUpdate charge expirationPATCHExtends or shortens the window during which a charge can still be paid.

Customer, 4 operations

create_customerCreate customerPOSTRegisters a payer with a tax identifier so charges can reference them by correlationID.
get_customerGet customerGETReturns a single payer record.
list_customersList customersGETReturns the registered payers together with paging counters.
update_customerUpdate customerPATCHChanges name, contact details, tax identifier or address of a registered payer.

Webhook, 3 operations

create_webhookCreate webhookPOSTSubscribes an endpoint to one OpenPix event such as a completed charge or a received Pix.
delete_webhookDelete webhookDELETERemoves a webhook so its URL stops receiving deliveries.
list_webhooksList webhooksGETReturns the webhook subscriptions of the account with the event each one listens to.

Qrcode, 2 operations

create_static_qrcodeCreate static qrcodePOSTProduces a QR code that can be printed once and paid many times.
list_static_qrcodesList static qrcodesGETReturns the reusable QR codes with their payloads and identifiers.

Refund, 2 operations

create_charge_refundCreate charge refundPOSTSends money back to the payer of a charge and returns the refund record.
list_charge_refundsList charge refundsGETReturns the refunds attached to a charge with their status and amounts.

Transaction, 2 operations

get_transactionGet transactionGETReturns a single money movement including the debit and credit party bank details.
list_transactionsList transactionsGETReturns the money movements of the account, each linked to the charge or QR code that produced it.

Use OpenPix from Claude Code, Cursor or Codex

Connect OpenPix in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its OpenPix operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect OpenPix

Create your workspace
Sign up free. Nothing to install.
Connect OpenPix once
Add your OpenPix connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

OpenPix integration FAQ

What can you do with the OpenPix integration?

LiveContext exposes 18 operations on OpenPix, covering charge, customer, webhook and qrcode. Common uses include polling a charge until it is paid, auditing which printed QR codes exist and correcting the email of a registered payer.