For AI agents
This site can be read and called by machines. Below: what is free, which tools are available, and the file that is the reference.
Tools
The reference file is /api/v1/tools.json.
describe_datasetget_schemaget_samplelookup_recordsearch_by_namerequest_dataset
What is free
- every page of the site
- the search index (static JSON fragments, CORS open)
- llms.txt
What is reserved
- a dated PDF report on one entity ($19)
- bulk matching of a list (CSV)
- monitoring of a list
Source and date
- Texas Comptroller of Public Accounts, Texas Open Data Portal
- 2026-10-01
- 474,859 entries in the index
Other registers
Catalogue of other public registers available in the same format: registres.pages.dev
The level of service we hold ourselves to
Regulation (EU) 2023/138 requires States to publish certain datasets — called high-value — free of charge, in machine-readable form, with an API and bulk download. We apply this level of service to this register, whether the law requires it or not.
- Free of charge — every page and every machine file on this site is open, with no account and no key.
- Machine-readable — manifest, field schema, real sample.
- With an API — 6 callable tools, described with their input schema, wired into the page for an agent, and the portfolio's MCP server.
- Bulk download — ⚠️ not served free here: the raw data can be downloaded free from the source, named in the footer; our normalised version is described on the data page.
⚠️ This register is not designated “high-value” in law: it is a level of service we set ourselves, not a regulatory guarantee. Details for agents · catalogue.
Machine gateway6/96 tools exposed
This is not a label: each line links to the file that proves it, and the ones that are missing are written down too.
- ✓versioned manifest
- ✓field schema, with fill rates
- ✓real sample
- ✓tools declared and served
- ✗free bulk download
- ✗callable MCP server
- ✓llms.txt
- ✓clean 404 page
- ✗log of agent visits on THIS site
An example that works, end to end
The example starts from the get_sample tool, which reads the served sample.
Prompt to give an agent
Use the get_sample tool of texas-taxpayer-permit-records.pages.dev and summarise the first three entries.What the tool returns
| id | 17515166332 |
|---|---|
| url | https://texas-taxpayer-permit-records.pages.dev/search/#r=17515166332 |
| fragment | https://texas-taxpayer-permit-records.pages.dev/d/r/874.json |
| name | LANDMARK INTERIOR BUILDERS, INC. |
| city | KRUM |
| state | TX |
| type | Construction |
| fields | {'Texas taxpayer number': '17515166332', 'Organization type': 'Texas profit corporation', 'Sales tax outlets with an active permit': '1', 'First sales date on file': 'Aug 1, 2016', 'Latest outlet permit issued': 'Aug 3, 2016', 'Outlets': 'LANKMARK INTERIOR BUILDERS, INC., Krum'} |
The same register can be queried through the portfolio MCP server (tools describe_register, get_schema, get_sample).
Reading one record by its identifier
The lookup_record tool takes the 11-digit Texas taxpayer number (e.g. 17515166332). For 17515166332 it reads https://texas-taxpayer-permit-records.pages.dev/d/r/874.json (hash of the identifier: h = 0, then for each character h = (h*31 + character code) modulo 4096; in hexadecimal on 3 digits) and returns the record shown at https://texas-taxpayer-permit-records.pages.dev/search/#r=17515166332. Checked when the site was built.