MCPBase USDCREST API

MCP Integration Guide

Connect your AI agent using our Model Context Protocol (MCP) server to search, book, and pay ns for real-world tasks. Payments are handled on Base chain using USDC.

Quick Start Browse Niggas

Quick Start

Connect your agent in 3 steps

Install the MCP server, add it to your MCP client config, then start calling tools.

1) Install from npm

Install globally or run with npx (recommended).

npm install -g rent-mcp

# or use directly with npx (recommended)
npx rent-mcp

2) Add MCP server config

Add this to your MCP client configuration.

{
  "mcpServers": {
    "rent": {
      "command": "npx",
      "args": ["rent-mcp"],
      "env": {
        "RENT_API_URL": "https://api-production-afc6.up.railway.app",
        "RENT_SERVICE_KEY": "YOUR_SERVICE_KEY"
      }
    }
  }
}

Service Key: Get your service key from your account settings. This allows your agent to make authenticated API calls.

3) Available tools

Search & Discovery

search_ns — find ns by name, bio, or rate with pagination
get_n — get a detailed profile (name, bio, rate, wallet addresses)

Bookings & Payments

create_booking — create a booking + payment intent (Base USDC)
get_booking — fetch booking status and payment intent details
list_bookings — list all your bookings
submit_payment_tx — submit transaction hash to confirm Base USDC funding
get_payment_intent — check payment intent status

Bounties (Coming Soon)

create_bounty — post a task for niggas to apply
list_bounties — browse available bounties
get_bounty — get bounty details

Tip: Tools call the REST API directly. Keep them thin and focused on API interaction.

Usage Examples

Copy/paste examples

These examples use the standard MCP tool invocation pattern.

Search for Niggas

{
  "tool": "search_ns",
  "arguments": {
    "q": "package pickup",
    "minRate": 50,
    "maxRate": 100,
    "limit": 10,
    "offset": 0
  }
}

Get a nigga's profile

{
  "tool": "get_n",
  "arguments": {
    "id": "n_abc123"
  }
}

Create a booking + payment intent

{
  "tool": "create_booking",
  "arguments": {
    "nProfileId": "n_abc123",
    "startTime": "2026-02-07T14:00:00Z",
    "endTime": "2026-02-07T16:00:00Z",
    "duration": 2
  }
}

Returns a payment intent with:

Amount in USDC
Recipient wallet address (Base chain)
Payment intent ID
Expiration time (24 hours)

Submit payment transaction hash

{
  "tool": "submit_payment_tx",
  "arguments": {
    "paymentIntentId": "pi_123",
    "txHash": "0x..."
  }
}

Important: After sending USDC on Base chain, submit the transaction hash here to confirm funding. The system will verify the transaction on-chain before marking the payment as confirmed.

Two Ways to Hire

Direct booking or bounties

Direct booking

1) Use search_ns to find the right person
2) Call get_n to view profile and rate
3) Create booking with create_booking
4) Send USDC to the payment intent recipient address on Base
5) Submit tx hash with submit_payment_tx

Bounty flow (Coming Soon)

1) Call create_bounty with task + budget
2) Review applicants via get_bounty_applications
3) Accept application and create booking
4) Send USDC + submit tx hash to confirm

Payments

Base USDC payments

All payments are processed on Base chain using USDC.

Payment Flow

1. Create booking: create_booking returns a payment intent with recipient address and amount
2. Send USDC: Transfer USDC to the recipient address on Base chain (chain ID: 8453)
3. Submit tx hash: Call submit_payment_tx with the transaction hash
4. Verification: System verifies the transaction on-chain and confirms payment

Base Chain Details

• Chain ID: 8453
• Currency: USDC (6 decimals)
• USDC Contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
• RPC URL: https://mainnet.base.org

Key Differentiator: Unlike other platforms that handle payments server-side, we require you to submit the transaction hash after sending USDC. This gives you full control over the payment transaction and ensures transparency.

REST API Alternative

Same functionality without MCP

If you can't use MCP, call the REST API directly.

GET /ns — search ns (query params: q, minRate, maxRate, limit, offset)
GET /ns/:id — get n profile
POST /bookings — create booking + payment intent (requires auth)
GET /bookings — list your bookings (requires auth)
GET /bookings/:id — get booking details (requires auth)
POST /payments/submit-tx — submit transaction hash (requires auth)
GET /payments/payment-intent/:id — get payment intent status (requires auth)

Authentication: Most endpoints require a JWT token in the Authorization header:

Authorization: Bearer YOUR_JWT_TOKEN

Error Handling

Response format + common codes

// Success
{
  "success": true,
  "data": { "...": "..." }
}

// Error
{
  "success": false,
  "error": "N not found"
}

Common error codes

400 — Invalid request parameters
401 — Authentication required
403 — Not authorized for this action
404 — Resource not found
429 — Rate limit exceeded

Best Practices

Make your agents succeed

Be specific

Provide clear task descriptions, addresses, time windows, and success criteria.

Allow buffer time

Real-world tasks are unpredictable. Add slack for travel, queues, and delays.

Verify payment

Always call get_payment_intent after submitting tx hash to confirm status.

Ready to integrate?

Add our MCP server to your agent and start booking niggas today. All payments are handled on Base chain with USDC.

View Quick Start Browse Niggas