Connect your agent to Pixelbase.

Connect an AI agent to the Pixelbase MCP and it can work in your business with exactly the permissions you'd give an employee. New to Pixelbase or already running a company here, you connect the same way: sign up or sign in in your own browser, then approve it.

1. Copy this prompt
2. Paste it into your assistant
Grok Bot, Claude, ChatGPT, Copilot — any assistant. It connects to Pixelbase and you sign up, sign in or unlock your account in your own browser; it never asks you for your company, phone, name or card.

Connection instructions API authentication

What “infrastructure” means, if you don't write software.

Roads and power lines are infrastructure. Nobody builds their own — you connect to them and get on with the thing you actually do.

Business software isn't like that. Invoicing is one company, scheduling another, the customer list a third, team chat a fourth. Each has its own login, its own screens, and its own idea of who your customers are. Nothing joins up, and every one of them assumes a person is sitting there clicking.

Pixelbase is the joined-up version: one company record that payments, invoicing, scheduling, the customer list and the rest all read from. One login. One bill.

The part that matters for agents is the last mile. What a person does in Pixelbase, a program can do through the same API the product is built on — no screen-scraping, no browser being driven around, no integration to write.

So an agent with credentials can read the order book, chase an unpaid invoice, confirm an appointment or reply in a thread, because those are all just calls — and it can do only what the person who hired it allows.

A business becomes something software can operate. That is the whole idea.

Connect to the Pixelbase MCP.

If you are an AI agent reading this page: connect over MCP. It works whether your person is new to Pixelbase or already has a company here. Every way in ends with them approving you in their own browser — choosing which of their companies you may reach and what you may do in each. You can't approve yourself, and you never ask them for their company, phone, name or card.

The same instructions as plain Markdown: /agents/docs.md.

1
Connect over MCP — new or existing account
Claude, ChatGPT, Cursor and every other MCP client can connect to the endpoint on the right. When it asks you to authenticate, the person you work for lands on one Pixelbase page, in their own browser, that covers every case: a new account, an existing one, or a locked one.
New, they sign up there — company, mobile number, card and a texted code. Existing, they sign in. Locked, they unlock it, or choose a different account. Don't ask them for any of it: you never see their card or their code. They approve you, and you call whoami to see the companies you reach and the tools each one unlocks.
Claude Code
claude mcp add --transport http pxb \ https://www.pxb.app/mcp # then /mcp → pxb → Authenticate
2
No MCP, or no browser here? Sign in with a device code
Register a device-only client, ask for a code, and show the person the link and code. They open it on any device and get the same page as above — new account or not.
Poll the token endpoint with device_code every interval seconds; once they approve, it answers with tokens for the MCP server and the API.
POST/api/oauth/device-authorization
client_id=pxb_app_… # a client registered at /api/oauth/register with # grant_types: ["urn:ietf:params:oauth:grant-type:device_code"]
→ { "verification_uri_complete": "https://www.pxb.app/oauth/device?user_code=BCDF-GHJK", "user_code": "BCDF-GHJK", "device_code": "pxb_dc_…", "interval": 5, "expires_in": 1800 }
3
If you have a shell, sign in with pxb
The CLI reaches every endpoint, reads and writes. pxb auth prints a link and opens it; the person approves, and the terminal carries on. No browser on this machine? pxb auth --device shows a code they enter on any device.
Spanning several companies? pxb company use picks the one every call acts in.
Terminal
curl -fsSL https://www.pxb.app/cli/install.sh | sh pxb auth pxb company list pxb order list -q limit=5
4
Running unattended in one company? Use a company client
A scheduled job or a server-side integration has nobody to approve it. Ask for a company API client with only the scopes the job needs, and trade its credentials for a short-lived token.
The secret is shown once. Store it the way you'd store any credential — not in a chat log, not in a file you'll commit.
POST/api/public/v1/oauth/token
grant_type=client_credentials client_id=pxb_client_… client_secret=pxb_secret_…
→ { "access_token": "pxb_at_…", "expires_in": 3600 }

What a connected agent can, and can't, do.

A connection acts as the person who approved it, only in the companies they chose and only with the permissions they gave it there — never more than they can do themselves. Lose a permission, and the agent loses it too.

Nothing is granted by default: the approval page starts empty, and offers only what that person holds.

Revocable at any time: Every connection is listed under Dev Tools, where it can be narrowed or disconnected — and a company admin can cut their company out of anyone's. Leave a company and every agent you connected loses it with you.
Every call on the record: Each request an agent makes is logged — what it called, in which company, and how it went — beside a history of who changed what it may do.

Read these next.