canonical: https://jentic.com/apis/schooldigger.com/schooldigger

# SchoolDigger API V1

Get detailed data on over 120,000 schools and 18,500 districts in the U.S. The API exposes 6 endpoints.

## For AI agents

Programmatically returns a list of districts, returns a detailed record for one district. Covers 6 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Returns a list of districts
- Manage developer tools data programmatically
- Integrate SchoolDigger API V1 into automated workflows
- Query and filter SchoolDigger API V1 records by parameters
- Monitor SchoolDigger API V1 operational status and events

## Use cases

### Developer Tools Operations

Use the SchoolDigger API V1 to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including returns a list of districts, returns a detailed record for one district, returns a schooldigger district ranking list.

Example prompt: Call GET `/v1/districts` to returns a list of districts

### Automated Districts Management

Automate districts operations by combining multiple SchoolDigger API V1 endpoints. Agents can returns a detailed record for one district and then returns a schooldigger district ranking list in a single workflow.

Example prompt: Call GET `/v1/districts/{id}` to returns a detailed record for one district, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SchoolDigger API V1 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'returns a list of districts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/districts` | Returns a list of districts |
| GET | `/v1/districts/{id}` | Returns a detailed record for one district |
| GET | `/v1/rankings/districts/{st}` | Returns a SchoolDigger district ranking list |
| GET | `/v1/rankings/schools/{st}` | Returns a SchoolDigger school ranking list |
| GET | `/v1/schools` | Returns a list of schools |
| GET | `/v1/schools/{id}` | Returns a detailed record for one school |

## Key resources

- **Districts** — Operations for districts
- **Rankings** — Operations for rankings
- **Schools** — Operations for schools

## Why Jentic

- **Setup:** Wiring the SchoolDigger API V1 by hand means standing up its request layer, tracking the paging on district and school lookups, and building your own retry handling against api.schooldigger.com. Through Jentic you install once, import SchoolDigger from the API Directory, store its credential once, and your agent calls it.
- **Permission scoping:** SchoolDigger exposes read-only lookups over districts, schools, and rankings, so you limit the agent to the operations it needs, such as listing districts or fetching a school by id. You choose the operations it may call, and any you leave out stay unavailable to the agent.
- **Credential handling:** Your SchoolDigger credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'return a list of districts' or 'look up a school by id', and Jentic returns the matching SchoolDigger operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the SchoolDigger API V1 use?

The SchoolDigger API V1 uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I returns a list of districts with the SchoolDigger API V1?

Yes. Use the GET `/v1/districts` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SchoolDigger API V1?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I returns a list of districts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns a list of districts'. Jentic returns the matching SchoolDigger API V1 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SchoolDigger API V1 have?

The SchoolDigger API V1 exposes 6 endpoints covering districts, rankings, schools operations.

### Can I limit what my agent is allowed to do with the SchoolDigger API?

Yes. Because you run Jentic One yourself, your own rules decide which SchoolDigger operations the agent may call. The SchoolDigger API is read-only over districts, schools, and rankings, so you can allow just the lookups it needs, such as listing districts or fetching a school by id, while leaving out ranking or school-list calls. Any operation you do not grant stays unavailable to the agent, and its stored credential is injected only at execution time.