DEVELOP · AGENTS

CONNECT GROK TO BITMAP

Bring your own Grok bot — or any AI agent that speaks MCP. It reads your BITMAPs, parcels, floors and leases, and can suggest builds for your land. You pay for your own AI; BitmapWin never runs it for you.

MCP ENDPOINT
https://bitmapwin.app/mcp

SCHEMAS
https://bitmapwin.app/api/public/agent-schema

STEP 01

ADD THE SERVER TO YOUR AGENT

Any MCP client with remote-server support takes this config. Clients that handle sign-in themselves will open a BitmapWin login window the first time.

{
  "mcpServers": {
    "bitmap": {
      "url": "https://bitmapwin.app/mcp"
    }
  }
}

STEP 02

SIGN IN AS YOURSELF

Every tool acts as the signed-in BitmapWin account, so your agent sees only what you can see. The server uses standard OAuth 2.1: an MCP client signs you in and keeps the token. If you call Grok through the xAI API directly, you pass that access token yourself — treat it like a password and keep it in an environment variable.

STEP 03

CALL IT FROM GROK (xAI API)

xAI's Responses API can attach remote MCP servers as a tool. Example in Python (field names follow xAI's remote MCP docs; check them for the latest models):

import os
from openai import OpenAI

client = OpenAI(api_key=os.environ["XAI_API_KEY"], base_url="https://api.x.ai/v1")

resp = client.responses.create(
    model="grok-4",
    tools=[{
        "type": "mcp",
        "server_label": "bitmap",
        "server_url": "https://bitmapwin.app/mcp",
        # Your own BitmapWin access token (see step 2). Never share it.
        "authorization": os.environ["BITMAP_TOKEN"],
    }],
    input="List my BITMAPs, then find open parcels on the oldest one.",
)
print(resp.output_text)

STEP 04

GIVE IT A JOB

A starter prompt that surveys your land and proposes a build:

You are my BITMAP land manager, connected to the BitmapWin MCP server.
1. Call my_bitmaps and pick my oldest BITMAP.
2. Call get_parcel_boundaries and inspect_build for it.
3. Design a small build that stays inside my own parcel rect.
4. Send it with submit_build_proposal as [x, y, z, kind] voxels.
5. Tell me what you proposed. Never claim it is inscribed — I approve it with my wallet.

TOOLS

WHAT YOUR AGENT CAN DO

search_bitmapsSearch the BITMAP registry by height, club or holder.READ

get_bitmapOne BITMAP: claim, block stats, build page and live bids.READ

get_parcel_boundariesParcel tile rights derived from the block (Mondrian rects).READ

discover_open_parcelsUnbuilt parcel tiles with live holders.READ

inspect_buildWhat is already built on a BITMAP or parcel.READ

get_floor_pricesCheapest real open listings.READ

get_lease_statusWho may build on a BITMAP during a lease.READ

recent_buildsWhat people are building right now.READ

get_bitmap_activityFull event timeline of one BITMAP.READ

my_bitmaps · my_bids · my_bit_balanceYour own holdings, bids and BIT.YOURS

get_portfolio_activity · my_watchlistOne stream across BITMAPs you own or watch.YOURS

watch_bitmapAdd or remove a BITMAP from your watchlist.YOURS

submit_build_proposal · my_build_proposalsSave a build suggestion on your own ground and list them.PROPOSE

SAFETY RULES

▸ Agents read and propose. They never sign, pay, inscribe or move sats.
▸ Build proposals are checked against live ownership and clipped to your own parcel ground.
▸ A proposal only becomes real when you open it and approve it with your own wallet.
▸ Your agent cannot see or write to anyone else's account.

[ SDK REFERENCE ][ PUBLIC API ][ LAND FORGE ]