This section describes how to set up your environment, configure the MCP client, and start using Interlace Agent Card tools.

Integration Workflow

To start using the Interlace Agent Card, complete the following steps.

Step 1 — Create a Developer Account

1. Visit the Agent Developer Page and register a developer account.
   1. Sandbox: https://agent-card-staging.interlace.money/
   2. Production: https://agent-card.interlace.money/
2. Sign in to access the developer dashboard.

Step 2 — Generate an API Key

1. In the Developer Page, navigate to API Key Management.
2. Click Create New API Key. The system will generate an API key in the format: itl_sk_xxxxxxxx... .

Step 3 — Configure the MCP Client

1. Configure the generated API key in your agent client. Supported clients include OpenCode, Codex, and other MCP-compatible clients.
2. After configuration, restart your agent client. The agent will automatically connect to the MCP server and discover available tools.

Example Configuration (OpenCode)

{
  "mcpServers": {
    "interlace": {
      "type": "remote",
      "url": "https://mcp.interlace.money/sse",
      "headers": {
        "Authorization": "Bearer itl_sk_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Usage Examples

The following examples illustrate how an agent can perform common tasks using natural language instructions and corresponding MCP tools.

1. Create a Card

• User request: Create a $10 card.
• Tool invoked: issue_card

Required Parameters

Response Fields

After the user transfers sufficient funds (USDC or USDT) to the depositAddress, the system will automatically load the balance onto the card. The card can then be used for online payments.
The funding address can be displayed as a static QR code for direct on-chain payment.

2. Get Card Details

When an online payment needs to be completed (for example, subscribing to a service), the agent invokes get_card to retrieve payment details such as the card number and CVV.

Response Fields

3. View Transaction History

• User request: How much has my card spent?
• Tool invoked: get_transactions

Request Parameters

Response Fields

4. Delete a Card

• User request: Delete this card and return the remaining balance.
• Tool invoked: delete_card

Response Fields

After the card is deleted, the remaining balance is automatically returned to the user's crypto wallet in the original funding currency (USDC or USDT). Withdrawal functionality will be introduced in a future release.

5. View On-Chain Top-Up History

• User request: How much has been deposited into my wallet?
• Tool invoked: list_topup

Request Parameters

Response Fields

6. Refund High-Risk Top-Up Funds

• User request: Refund my funds on hold.
• Tool invoked: refund_topup

Request Parameters

Response Fields

7. View Wallet Balances

• User request: What's my current wallet balance?
• Tool invoked: list_wallet_balances

Response Fields

8. Withdraw Wallet Balance

• User request: Withdraw funds from my wallet.
• Tool invoked: get_withdraw_link

Response Fields

After receiving the withdrawal URL, the user can open the page and submit the withdrawal request by providing the currency, blockchain network, destination address, and withdrawal amount.

9. View On-Chain Withdrawal Status

• User request: Check my withdrawal status.
• Tool invoked: list_withdraw_transfers

Request Parameters

Response Fields

Important Notes

1. Card Limit

• Only one active card is allowed per user. A new card cannot be created until the existing card is deleted.
• Card with status CONTROL, ACTIVE, PENDING, or FROZEN is considered active. INACTIVE indicates a deleted card.

2. Spending Limit

• Each card has a lifecycle spending limit of $20. Once the limit is reached, the card is automatically disabled.

3. Transaction Restrictions

• Agent Card supports online transactions only, such as e-commerce, subscriptions, and other digital services.
• POS and ATM transactions are not supported.
• Merchant category restrictions (MCC controls) apply.

4. Data Security

• Full card details (e.g., PAN, CVV) are available only through MCP tools and are not displayed in the Developer Page.
• Ensure your agent client securely stores and handles sensitive payment data.

5. Balance Refund

• After deletion, any remaining balance is automatically returned to the user's crypto wallet in the original funding currency (USDC or USDT).
• Wallet balances can be withdrawn to external blockchain addresses at any time via the get_withdraw_link tool.

6. Funding Requirements

• Use supported currencies (USDC / USDT) and networks. See the Supported Chains and Currencies for the full list.
• The deposited amount must be equal to or greater than the expected funding amount. Funds are automatically credited once sufficient.
• If the deposited amount is insufficient, funding will not be processed. You may send additional funds to the same address.
• When the funding status is ONHOLD, the funds are temporarily held and can be refunded using the refund_topup tool.