← Back to FieldSmith Home
FieldSmith Logo
FieldSmith Agent Protocol

FieldSmith for Grok Bot & Autonomous Agents

• Live Agent Endpoints • WebMCP on Checkout • Link Wallet Compatible

This protocol specifies how Grok Bot (on its persistent Agent Computer cloud browser), Claude, and autonomous purchasing agents interact with FieldSmith Pro to onboard trade contractors (roofers, plumbers, tile setters, electricians, HVAC).

The Product Boundary (The Split)

Grok Bot handles discovery, configuration, and payment initiation. Grok Bot cannot touch the contractor's physical mobile device or carrier network.

✓ What the Agent Does

  • Select plan from llms.txt / pricing
  • Collect business name, trade, service area, and quote policy
  • POST signup payload to API
  • Open Stripe Checkout in browser
  • Trigger Stripe Link single-use token or prompt user to approve charge
  • Poll until paid_pending_phone

✗ What the Agent Does NOT Do

  • Never types raw credit cards into chat
  • Cannot install Android companion app
  • Cannot dial carrier star codes (*72 / *71)
  • Cannot complete carrier SMS phone verification
  • Must stop and hand off to contractor

Agent Instructions (System Directive)

If you are an AI assistant or Grok Bot, copy and obey this directive:

# FieldSmith Protocol for Grok Bot

You may buy a subscription and fill setup.
You may not install the Android app, dial *72, or complete SMS number verify.
Those require the contractor's phone.

## Pay
1. POST https://api.fieldsmith.pro/api/agent/signup with contractor JSON.
2. Open checkout_url in the browser.
3. Use Stripe Checkout / Link. Never type a card number from chat.
4. Wait for the human to approve the charge if Grok Bot asks.
5. Poll GET https://api.fieldsmith.pro/api/agent/signup/{id} until status is "paid_pending_phone" or "active".

## Then Stop
Tell the user: "Install the FieldSmith Android app and dial *72 to forward calls.
We texted setup instructions to your phone."

Do not invent a forwarding number. Do not claim the receptionist is live until status is active.

1. Agent Signup Endpoint

POST https://api.fieldsmith.pro/api/agent/signup

Creates a pending contractor tenant record and returns a prefilled Stripe Checkout URL preloaded with the buyer's email and client reference ID.

Request Body (JSON)

{
  "email": "owner@shop.com",
  "plan": "pro",
  "business_name": "Apex Flooring",
  "trade": "tile_shower",
  "service_area": "Polk County, FL",
  "estimate_policy": "photos first, written estimate same day",
  "owner_cell": "+18635550144"
}
FieldTypeRequiredDescription
emailstringYesContractor's email for receipts & account binding
business_namestringYesShop / trade company name (e.g. Apex Flooring)
planstringNosolo ($49.99/mo), pro ($79.99/mo), or vip ($380/yr). Default: pro
tradestringNoVertical: tile_shower, roofing, plumbing, hvac, etc.
service_areastringNoTarget territory or counties (e.g. Polk County, FL)
estimate_policystringNoIntake quote policy (e.g. photos first)
owner_cellstringNoContractor personal phone number in E.164 format

Response (HTTP 200 OK)

{
  "id": "fs_63eaa218f8d1",
  "checkout_url": "https://buy.stripe.com/aFa3cveNXa0Q1g12CcaVa04?prefilled_email=owner%40shop.com&client_reference_id=fs_63eaa218f8d1",
  "status": "pending_payment",
  "message": "Open checkout_url in browser. Use Stripe Checkout / Link. Agent stops at paid_pending_phone."
}

2. Polling Status Endpoint

GET https://api.fieldsmith.pro/api/agent/signup/{id}

Poll this endpoint every 5–10 seconds after opening checkout_url in the cloud browser.

Response States

StatusMeaningAgent Action
pending_paymentAwaiting user approval in Stripe CheckoutContinue polling; assist user with approval
paid_pending_phonePayment verified; line allocatedSTOP! Instruct human to install app & dial *72
activeContractor dialed *72; liveCongratulate user. Receptionist is active.
canceledSession expired or failedPrompt user to restart signup

3. Streamable HTTP MCP Server (Model Context Protocol)

FieldSmith Pro provides a remote Model Context Protocol (MCP) server over Streamable HTTP. Compatible with Grok Bot Custom Connectors, SuperGrok, Claude Desktop, and OpenAI Agent SDKs.

ParameterValue
Endpoint URLhttps://api.fieldsmith.pro/mcp
TransportStreamable HTTP (JSON-RPC 2.0)
Protocol Version2024-11-05
AuthenticationPublic (no auth required for catalog/signup)

Available MCP Tools

Connecting in Grok

  1. In Grok chat, navigate to Connectors → New Connector → Custom.
  2. Enter the public HTTPS MCP URL: https://api.fieldsmith.pro/mcp.
  3. Save connector. Grok can now query plans, register trade shops, and trigger checkouts autonomously.