Agents (MCP)
Connect an agent (MCP)
Drive the REB engines from Claude or any MCP client — same auth, same metering.
Connect#
Create a key in the Developer Console. On creation you get a ready-made connector URL with the key embedded — paste it into a custom connector. Prefer headers? Use a Bearer token instead.
Connect
# The connector URL (from the console — embeds your key):
https://www.reelestateboss.com/api/mcp?key=reb_live_…
# Or with a Bearer header (JSON-RPC 2.0):
curl https://www.reelestateboss.com/api/mcp \
-H "Authorization: Bearer reb_live_…" \
-H "Content-Type: application/json" \
-d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }'Tools#
| Field | Type | Description |
|---|---|---|
| list_models | read | List the live engines you can generate with. Free — never metered. |
| generate | billed | Run any live engine by id. Returns a task id; poll with task_status. |
| listing_enhance | billed | Raw listing photo → MLS-grade REB-look edit. Returns a task id. |
| task_status | read | Check a task by id; returns status and, when done, output URLs. |
Call a tool#
tools/call
curl https://www.reelestateboss.com/api/mcp \
-H "Authorization: Bearer reb_live_…" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0", "id": 2, "method": "tools/call",
"params": { "name": "listing_enhance", "arguments": { "image_url": "https://…/raw.jpg" } }
}'
# → returns a task id; call task_status to poll for the output URL.Security#
The ?key= mode puts your key in the URL — treat that URL as the secret it contains, share it only over HTTPS, and revoke + rotate the key if it leaks. Set a spend cap on the key so a runaway agent can never exceed your budget.