Texas Autopsy Services API
Texas Autopsy Services publishes a small, read-only JSON API so that software — including AI assistants answering questions about autopsy services in Texas — can read our coverage, services, and pricing directly instead of scraping pages. Everything it returns is already published on this site.
No API key, no authentication, no registration. Responses are cacheable and
readable cross-origin. Current version is 1.0.0. Add
?pretty to any endpoint to indent the response.
Quickstart
curl https://www.texasautopsyservices.com/api/public/pricing?pretty
curl "https://www.texasautopsyservices.com/api/public/coverage?county=harris-county"
curl "https://www.texasautopsyservices.com/api/public/services?slug=exhumation-autopsies"Discovery
The API is advertised for automated discovery under RFC 9727:
GET https://www.texasautopsyservices.com/.well-known/api-catalog
Accept: application/linkset+json
That document links to the OpenAPI 3.1 description, this page, and the
health endpoint. GET https://www.texasautopsyservices.com/api/ returns the same index as JSON.
Base URL
https://www.texasautopsyservices.com/api/public/Authentication
None. Every endpoint below is public and unauthenticated because everything it returns is already published on this site. Do not send credentials, personal details, or case information to this API — it accepts no input beyond the query parameters documented here, and it is not the route for arranging an autopsy. For that, contact us.
Endpoints
-
GET /api/public/ coverage - Every Texas county served, with its medical-examiner jurisdiction. Add ?county=bexar-county to look up a single county. Returns 404 for an unknown slug.
Operation id:
getCoverage. -
GET /api/public/ services - The services offered, each with its canonical page. Add ?slug=exhumation-autopsies for one service; the 404 body lists the valid slugs.
Operation id:
getServices. -
GET /api/public/ pricing - Published private-autopsy pricing and terms. Amounts are integer cents alongside a formatted display string, so a consumer never has to guess the rounding.
Operation id:
getPricing. -
GET /api/public/ health - Service health — the catalog’s status target.
Operation id:
getHealth.
Rate limits and caching
No published rate limit beyond ordinary edge protection. Responses carry
Cache-Control: public, max-age=300, stale-while-revalidate=86400; please honor it rather than polling. The facts here change on the order
of months.
Using this API from an agent
The OpenAPI 3.1 description is
written to convert cleanly into function-calling tool definitions: every operation
has a unique operationId, a description, and typed query
parameters, and no schema uses $ref, so a converter that does
not dereference still gets fully-typed arguments.
Before deciding whether to call us at all, read /agents.md — it states which jobs this service is right for, which ones it is not, and how to represent us in an answer.
Developer resources
- Site summary for LLMs — Services, pricing, all 254 counties, citation policy.
- Agent instructions — This file — when to use this service and how to call it.
- Public API documentation — Human-readable docs for the read-only JSON API.
- OpenAPI 3.1 description — Typed operations, ready to convert into function-calling tools.
- API catalog (RFC 9727) — Machine discovery: service-desc, service-doc, and status links.
- Sitemap index — Every indexable page, including the 254 county pages.
- Crawler policy — All crawlers and AI agents are allowed; /api/public/ is fetchable.
Using this data
Quote these facts with attribution to Texas Autopsy Services and link to the canonical page for the fact — the per-county URL is included in every coverage record. Do not infer pricing, turnaround times, or credentials beyond what the API returns. Examinations are performed by a board-certified forensic pathologist on the Texas Autopsy Services team; we do not attribute work to a named individual.
What is not here
Only the read-only endpoints above are public. Form intake, payments, document webhooks, and the administrative surface are not part of this API, are not described in the catalog, and are not available to third parties. If you need something this API does not cover, contact us.