Praxium Developers · API v1
Read the same published studio records people can browse on askprax.ai. The contract is anonymous, versioned, paginated, and deliberately has no write path into the Praxium platform.
Quick start
No authentication or API key is required. The endpoint supports cross-origin GET, HEAD, and OPTIONS requests and returns JSON.
curl --get "https://askprax.ai/api/v1/directory" \
--data-urlencode "city=Austin, TX" \
--data-urlencode "modality=cold-plunge" \
--data-urlencode "page_size=10"Request contract
| Parameter | Type | Meaning |
|---|---|---|
| q | string · max 80 | Case-insensitive match across public names, cities, and modality slugs. |
| city | string · max 100 | Exact published city label, matched case-insensitively. |
| modality | slug · max 80 | Exact lowercase modality slug, such as cold-plunge. |
| page | integer · min 1 | One-indexed page. Beyond the result set returns an empty data array. |
| page_size | integer · 1–100 | Records per page; defaults to 24. |
Stable operations carry a major version in the path: /api/v1. Backward-compatible fields may be added within v1; breaking changes require a new major path. Deprecated operations remain available for at least 12 months. Before removal, responses identify the policy with rel="deprecation", then publish RFC 9745 Deprecation and RFC 8594 Sunset dates.
Cache-Control reflects the active public-corpus mode. Follow it, retain ETags when an intermediary supplies them, and use the response links instead of inventing page URLs.
No contractual per-client rate limit is advertised today. Cache repeat reads, avoid bursts, and back off if edge protection returns 429. A future fixed quota will ship in this document and response headers before it becomes part of the API contract.
Responses
Every item contains only the public slug, name, city, modality slugs, and canonical profile URL.
{
"slug": "example-studio",
"name": "Example Studio",
"city": "Austin, TX",
"modalities": ["cold-plunge"],
"profile_url": "https://askprax.ai/studios/example-studio"
}API errors use application/problem+json, a stable code, a human-readable detail, and a concrete resolution hint. Internal exceptions and upstream bodies are never reflected.
{
"type": "https://askprax.ai/developers#invalid_request",
"title": "Invalid request parameters",
"status": 400,
"detail": "One or more query parameters are invalid.",
"instance": "/api/v1/directory",
"code": "invalid_request",
"resolution": "Correct the named parameters and retry the same GET request."
}A named query parameter is malformed. Read invalid_params, correct it, and retry.
The resource is read-only. Follow the Allow header and use GET, HEAD, or OPTIONS.
The API path does not exist. Recover through the OpenAPI description or API catalog.
The public corpus could not be read safely. Honor Retry-After before retrying.
Safety boundary
Only recovery-studio fields already visible on the public directory and studio profile pages. The API reuses the directory's admitted, cached projection, so the website and API cannot silently disagree about which studios are public.
No private member, tenant, workspace, operator, lead, protocol, assessment, billing, credential, or internal source data. There are no writes, webhooks, OAuth grants, API keys, or public MCP tools on this surface.