Install with a prompt
Send this prompt to the agent in the Host you want to configure:https://api.clinkbill.com/mcp. For Sandbox integration, use the UAT endpoint in MCP connection and OAuth; keep the selected environment consistent throughout setup and testing.
Complete the connection
1
Install the Skill and register MCP
The agent uses the selected Host’s installation and MCP settings. The connection is named
clink and uses Streamable HTTP. A Host that cannot edit its own settings may ask you to add the connection manually.2
Authorize your wallet
Complete login and consent in the user-facing authorization flow. The Host must confirm that OAuth succeeded; writing the MCP configuration alone is not enough.
3
Check that the tools are visible
The Host should expose tools such as
get_skill_manifest, get_account_state, and get_credential. If it requires a reload, reload once and check the connection again.
The connection configuration does not need an API key or a pasted bearer token. The Host obtains the user’s tokens through OAuth.
Purchases still require a valid authorization after connecting. When passkey verification is requested, open the Agent’s link on your own device to confirm. See Passkeys and purchase authorization.
Read the current operating rules
After connection, the MCP server publishes tool schemas and operating rules. Read theclink://skill/rules resource. If the Host cannot read MCP resources, call:
tools/call parameter object, not a separate HTTP endpoint. Follow the returned rules for business operations. Rules can change without reinstalling the connection Skill.
Check your wallet
Ask the agent:get_account_state. An empty card list means the MCP connection can work while a payment card still needs to be added. If you want to add one, ask the agent to call start_payment_method_action with action: "add", then complete the returned setup link on your own device. See Wallet Service.
Checking cards is useful for setup or card selection; it is not a required preliminary call for every Browser Pay purchase.
Make a Browser Pay purchase
Choose an item you want to buy on a merchant website. Your Agent needs browser interaction capability. Replace the placeholder product URL below with the actual URL, and adjust the quantity and budget:1
Read the final checkout total
The Agent reaches the merchant’s card form and reads the final total, including shipping and tax, before requesting a payment credential. Your budget is the maximum you approved, not the amount to charge.
2
Complete any requested approval
If card setup or spending approval is needed, the Agent gives you a Clink action link. Open it on your own device and complete the requested steps, including Passkey verification when shown. Return to the same conversation; the Agent checks Clink’s status before continuing. If an existing authorization covers the purchase, this step may not be needed.
3
Check the purchase result
The Agent fills the card fields, submits the payment, reads the merchant’s result, and reports it to Clink. After an observed success, it should show the merchant, actual paid amount and currency, and any merchant order number displayed.
orderId is not a substitute. If the payment result cannot be confirmed, the Agent should say it is unknown and resolve the same purchase instead of paying again. See Browser Pay for payment steps and recovery.
When credentials are encrypted
When credentials are encrypted
The default independent-agent path returns card fields ready to use. If your connection returns
key and payload instead, follow the encrypted credential integration before filling the merchant form.