Query the public surface.

Overview

Base URL: https://pegegrid.com. The public sample contains active studios with at least probable confidence and a publishable name. Records include only facts whose own source policy permits publication. A withheld list names categories omitted from a record; it does not reveal their values.

Responses are JSON. The dataset release and generation timestamp are available at /v1/sample/meta.

Public REST

Search filters: city, service, room_type, equipment_category, has_pricing, has_rooms, has_website, and max_hourly_rate. Use limit (1–5) and page (1–2). Filters inspect public facts only, so a zero-result search does not prove a studio lacks that feature.

Search by city

curl -sS 'https://pegegrid.com/v1/sample/entities?city=Miami&limit=5'

Search public services or pricing

curl -sS 'https://pegegrid.com/v1/sample/entities?service=mixing'
curl -sS 'https://pegegrid.com/v1/sample/entities?has_pricing=true'

Fetch a record and metadata

curl -sS 'https://pegegrid.com/v1/sample/entities/{id}'
curl -sS 'https://pegegrid.com/v1/sample/meta'

Replace {id} with an entity_id from a search response. A record outside the sample returns 404. The search response includes data and pagination metadata; the metadata endpoint includes the current release, freshness, sample population, and facets.

Public MCP

The endpoint accepts stateless JSON-RPC over HTTP. Send initialize, then tools/list to discover tools. No bearer key is required.

curl -sS 'https://pegegrid.com/mcp/public' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Available tools

• sample_studios — search the bounded public sample with the REST filters above.
• sample_studio — retrieve one public record by entity_id.
• public_dataset_info — inspect release metadata, facets, and public limits.

curl -sS 'https://pegegrid.com/mcp/public' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"sample_studios","arguments":{"city":"Miami","limit":5}}}'

MCP tool results contain a structured JSON response. A request outside the public boundary returns a tool result with isError: true and an authenticated_access_required body.

Authenticated access

The full service uses separate endpoints: GET /v1/entities, GET /v1/entities/{id}, GET /v1/changes, GET /v1/meta, and POST /mcp. They require Authorization: Bearer <key>. The public MCP endpoint exposes none of the authenticated tools.

Requests for capabilities outside the public sample return HTTP 401 with authenticated_access_required and a stable capability name. This documentation does not imply that keys are self-service or that a paid plan exists.

Machine-readable docs

OpenAPI JSON describes only public REST routes. llms.txt summarizes the public interfaces and limits for agents.