AI agents and research assistants
Let a server-side agent retrieve structured school or district records, then show the source and year in its answer. Keys stay in your secure backend, not in a prompt, browser bundle or public repository.
Programmatic access is a paid product. Approved customers receive an individual API key after the use, geography, fields, request volume and license are agreed and paid.
The public site explains the data. The API is for systems that need cited school and district records repeatedly and securely.
Let a server-side agent retrieve structured school or district records, then show the source and year in its answer. Keys stay in your secure backend, not in a prompt, browser bundle or public repository.
Search, filter and join school profiles without maintaining federal source files yourself. Product embedding and redistribution are licensed explicitly; a spreadsheet purchase does not grant API or resale rights.
Return government-reported facts with citations and let the user decide. Integrations must not rate schools, describe neighborhoods as desirable, or use school data to steer housing choices.
Query consistent identifiers, profiles and field definitions across geographies. Journalists can still request one-off cited figures; recurring automated access belongs in a licensed API plan.
The exact fields and endpoints in your license depend on provenance, geography and intended use.
Identity, location, enrollment, staffing, program, finance and other available fields, with null values preserved instead of guessed.
Request records by state, city, district or identifier, with pagination for controlled programmatic retrieval.
Retrieve definitions, source agencies, source years and caveats so your interface can explain what each value means.
Large jobs may be delivered as files instead of repeated API calls. We choose the delivery method in the written scope before payment.
No anonymous production endpoint · no public API key · no promise of real-time agency data.
Tell us who will use it, whether an AI agent is involved, the geography, fields, expected requests and whether results appear in a customer-facing product.
We check source licensing, Fair Housing constraints, redistribution needs and whether the requested fields are available at the stated vintage.
You receive a written scope and price. API access is not included until payment is complete; custom terms apply to product embedding and high-volume use.
We issue an individual key, production base URL, allowed endpoints and usage limits. Calls are authenticated and metered. Keys can be revoked if exposed or used outside the license.
Yes. A licensed customer can connect an AI agent or application through a secure server-side integration. API keys must not be placed in public browser code or shared between unlicensed products.
No. Download licenses and programmatic API access are separate products because API usage, support, redistribution and request volume require a separate scope.
There is no anonymous public data endpoint. The free sample and public aggregate pages show field definitions and source quality; production credentials are issued only after scope approval and payment.
No. K12 Atlas integrates published federal and state records. Every field retains a source and vintage so an application can show when the underlying agency reported it.
We will confirm the fields, license, delivery method and price before payment. No key is issued through a public form.