> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clinkbill.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Independent Agent Quickstart

> Install the Clink Skill, connect MCP, and authorize your wallet in an agent Host.

Use this path for a personal agent, such as an agent running in Codex, or a bot whose Host supports remote MCP and OAuth. If you are building a service that connects multiple users, start with [Agent platform integration](/guides/agent/platform_integration).

## Install with a prompt

Send this prompt to the agent in the Host you want to configure:

```text theme={null}
Read and install https://www.clinkbill.com/SKILL.md in this agent Host.
Follow the Skill to register the Clink MCP connection and complete user OAuth.
Reuse an existing connection for the same environment and preserve other settings.
After setup, verify that Clink tools are available and report:
the selected Host, Skill installation status, MCP URL, OAuth status,
and whether a reload is needed.
Complete setup only; do not initiate a payment.
```

The official [Clink Skill](https://www.clinkbill.com/SKILL.md) is a single file for installation and connection setup. It connects to **Production** at `https://api.clinkbill.com/mcp`. For Sandbox integration, use the UAT endpoint in [MCP connection and OAuth](/guides/agent/mcp_integration); keep the selected environment consistent throughout setup and testing.

## Complete the connection

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

For manual setup, use the Host's documented configuration format with these connection values:

| Setting | Value |
| :- | :- |
| Connection name | `clink` |
| Transport | Streamable HTTP |
| Production MCP URL | `https://api.clinkbill.com/mcp` |
| Authentication | User OAuth, managed by the Host |

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](/guides/agent/wallet_service#passkeys-and-purchase-authorization).

## Read the current operating rules

After connection, the MCP server publishes tool schemas and operating rules. Read the `clink://skill/rules` resource. If the Host cannot read MCP resources, call:

```json theme={null}
{
  "name": "get_skill_manifest",
  "arguments": {
    "include_rules": true
  }
}
```

This is a `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:

```text theme={null}
Show the payment cards currently available in my Clink wallet and which one is the default.
```

The agent uses `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](/guides/agent/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:

```text theme={null}
Use Browser Pay and my Clink card to buy 1 item from:
https://shop.example.com/products/item
Keep the final total, including shipping and tax, within USD 25.
If it exceeds that amount, ask me before proceeding.
If checkout requires an address or contact details you do not have, ask me first.
After payment, tell me the merchant, actual paid amount and currency,
and the merchant order number if it is displayed.
```

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

A successful purchase summary should look like this, using values observed on the merchant page:

```text theme={null}
Merchant: <merchant name>
Result: Payment confirmed by the merchant
Paid: <actual amount> <currency>
Merchant order: <displayed order number, or "Not shown">
```

The merchant order number comes from the merchant; a Clink payment `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](/guides/agent/browser_pay) for payment steps and recovery.

<Accordion title="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](/guides/agent/browser_pay/decryption) before filling the merchant form.
</Accordion>

## Resolve setup issues

| What you see | Next step |
| :- | :- |
| Skill installed, but no Clink tools | Check MCP registration and the Host's reload requirements. Installing a file alone does not connect MCP. |
| OAuth pending or failed | Finish the active authorization flow, or use the Host's reconnect action after it fails. |
| Insufficient permission for a tool | Let the Host request the required OAuth scopes. If it cannot, reconnect with the scopes in the [OAuth guide](/guides/agent/mcp_integration). |
| No available card or spending authorization | Follow the wallet or payment tool's returned next action. Reinstalling the Skill does not set up a card. |
| Skill is outdated | Read the official Skill again and update this Host's installation. Preserve the selected environment and existing connection. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.