Developer platform · Network plan

The data and admin layer for maps.

Raw Mapbox renders a map. It does not host your data, geocode your addresses, give your team an admin UI, or handle filtering, embedding, and lead capture. Saw Your Sign is all of that, behind a REST API, a JavaScript SDK, live data bridges, an MCP server, and an agent skill.

$curl https://sawyoursign.com/api/v1/openapi.json

Start free trial Read the API spec

Everything you would otherwise rebuild.

Bring your data, or host it with us, and ship a branded, filterable, embeddable map. Each piece is documented and live today.

{ }

REST API

Bearer-token, scoped API for records, maps, leads, reviews, galleries, and record types. Addresses geocode server-side. Idempotency keys so retries never double-create a pin.

OpenAPI spec

</>

SDK + React

A JavaScript SDK and typed React components (<SawYourSignMap>, useMapItem). Drive the map from your own filters, react when a visitor picks a pin, read the selection outside the map, and run it headless.

SDK + React

⇄

Data bridges

Back a map with your own data, read live, nothing copied: a Postgres database, a CSV at a URL, a Google Sheet, or an Airtable base. Visitors filter only the fields you allowlist.

Data bridges

◇

MCP server

Connect Claude Desktop or any MCP client and let an agent read your workspace with a scoped, read-only token. The same tool layer as the in-app assistant.

MCP guide

✦

Agent skill

A portable Claude skill that drives the API: verify a token, add geocoded records, publish an embeddable map. Point an agent at your data and let it stand up the map.

SDK + skill

↗

Webhooks

HMAC-signed outbound webhooks with a 5-attempt retry, a delivery log, and replay. A new lead lands in your CRM or inbox with the record already attached.

Integrations

Ways in

Push records. Embed maps. Drive it with an agent.

Send a record and we geocode it and place the pin. Drop the SDK or the typed React components onto any page and steer the map from your own UI. Or hand a scoped token to an MCP client and let an agent read the workspace.

Bearer tokens + scopesIdempotency keysOpenAPI 3.1Signed webhooks

curl -X POST https://sawyoursign.com/api/v1/records \
  -H "Authorization: Bearer sys_live_t_…" \
  -H "Idempotency-Key: job_5821" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Roof replacement",
    "record_type": "job",
    "address": { "line1": "412 Birch Rd", "city": "Providence", "state": "RI" }
  }'

→ 201  pin created, geocoded & live

Data bridges

Bring your own data, read live.

A data bridge points a map straight at your source. Pins resolve at request time, so edits and new rows show up with nothing copied and no import to keep in sync. Visitors can only filter the fields you allowlist, and your credentials never reach the browser.

PostgreSQLCSV URLGoogle SheetsAirtable

In production: Cycling Compass, 14,000+ shops

data-bridge

# connect a Google Sheet, no developer
source   = "https://docs.google.com/…/edit"
columns  = { title, lat, lng, brands[], rating }

# the map reads it live
GET /m/{token}/pins?bbox=…
  → 14,697 pins  (cached 60s, filtered server-side)

→ edits in the sheet show up. nothing copied.

API resources

live data sources

rows copied to go live

script tag to embed

Build the map. Skip the plumbing.

Start free trial