PinkWallet Website Logo
Join early access
Agent builder · MicrosoftAgent key in the URLAbout 3 minVerified 2026-10-01

Connect Microsoft Copilot Studio to Pink Agentic AI Payments

Add Pink as a Model Context Protocol tool in Copilot Studio, using the key-in-URL form. Works with Agents built in Copilot Studio. Plans: Copilot Studio licence.

What you get

Microsoft Copilot Studio asks Pink before it pays

Once connected, Microsoft Copilot Studio can see its budget, the payees it may pay and the rules that apply, run a dry run, request a payment and file the receipt. The rules you set in Pink decide each request: allowed on the spot, sent to a person on the phone, or blocked. Microsoft Copilot Studio never holds a card number or a bank login.

Step by step

  1. 1

    Create a free sandbox workspace

    Open agentic-sandbox.pinkwallet.com, type a company name, pick a template (coffee shop, startup or e-commerce) and click Create workspace. You get an admin key for the console and one key per AI agent. Keep the admin key: the sign-in page asks for it.
    After creating a workspace: the admin key and one key per agent are shown once
    After creating a workspace: the admin key and one key per agent are shown once
  2. 2

    Copy an agent key

    From the workspace page or the console.
    After creating a workspace: the admin key and one key per agent are shown once
    After creating a workspace: the admin key and one key per agent are shown once
  3. 3

    Add the tool

    Open your agent, go to Tools → Add a tool → New tool → Model Context Protocol. Paste https://agentic-sandbox.pinkwallet.com/mcp/<agent_key> as the server URL and choose No authentication (the key in the URL identifies the agent). Give it the name Pink.
  4. 4

    Test in the studio

    Open the test pane, enable the Pink tool, and ask the agent to buy something. The seven tools appear under the tool's details.
  5. 5

    Watch the approval land in the console

    Open the sandbox console (link on the workspace page). Requests that cleared, asked a person or were blocked are all listed with the rule that decided them. Approve the pending one and the agent continues.
    Approvals in the console: the rule that stopped the request, the agent's reason, the evidence
    Approvals in the console: the rule that stopped the request, the agent's reason, the evidence

Try it: say this to Microsoft Copilot Studio

Say this

“Check my budget with Pink, then order 20 kg of espresso beans from Counter Culture Coffee for $420. After that, order $890 of weekly supplies from Sysco.”

What you will see

The first order is allowed on the spot and the agent receives a single-use test credential. The second stops at the store manager's rule ($500–$2,000): it shows up under Approvals in the console, and the agent waits for a person. Approve it there and the agent picks up the credential.

Why those two rules exist →

Pink's side, in three screens

The sandbox workspace page with the admin key and one key per agent
Keys are shown once when the workspace is created.
Pink's sign-in page: admin key, agent selector, Allow and Deny
Sign-in: choose which agent the app acts as.
The console's Approvals tab with a pending request
Requests that need a person wait here and on the phone.

FAQ

Does Copilot Studio support Pink's transport?

Yes. Copilot Studio supports Streamable HTTP MCP servers, which is what Pink speaks.

Can I use OAuth instead of the key in the URL?

Copilot Studio's OAuth setup needs a client id and secret entered by hand; for the sandbox the key-in-URL form is simpler. Production will offer a pre-registered OAuth client.

Official documentation

Menu names and settings paths follow each vendor's documentation at the verified date. If a vendor moves a menu, the linked page is the source of truth; the Pink side does not change.

Other clients