Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
District API (BYOK) icon

District API (BYOK)

Look up US school districts and schools by address, location or NCES id, with enrollment, grades and finance, using your own DistrictAPI key

Unify Dynamics LLC

Tools7read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderDistrict APIunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which school district covers 12865 Main St, Apple Valley, CA?
Tools called
lookup_district
Show me the profile of school district 0600017
Tools called
get_district
List the charter schools in district 0600017
Tools called
list_district_schools
Find school districts named Unified in California
Tools called
search_districts
Which schools are within 3 miles of 12865 Main St, Apple Valley, CA?
Tools called
find_schools_nearby
Show the profile of school 060001706027
Tools called
get_school

About

District API (BYOK) lets an AI assistant read your own District API data through the District API API with a key you supply (DistrictAPI key). Read-only: 7 tools (lookup_district, get_district, list_district_schools, search_districts, find_schools_nearby, get_school, get_school_district). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.districtapi.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by District API. District API and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the District API API (api.districtapi.dev) with a BYOK key; documentation: https://districtapi.dev/docs. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

7 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data7 tools
  • Lookup districtFind the school district that serves an address or a latitude/longitude, or fetch one by NCES id.
  • Get districtGet the full profile of one school district by its seven-digit NCES LEA id: location, grades, enrollment, per-pupil spending and school count.
  • List district schoolsList the open schools of a district, optionally only one school type or only charter schools.
  • Search districtsSearch school districts by name, state or county (at least one is needed).
  • Find schools nearbyFind schools within a radius of an address or a latitude/longitude, with type, grades, enrollment and charter, magnet or virtual flags.
  • Get schoolGet the full profile of one school by its twelve-digit NCES school id.
  • Get school districtGet the parent district of a school, given the school's twelve-digit NCES id.

Information

PublisherUnify Dynamics LLC
CategoryHome & lifestyle
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-districtapi.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 7 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-districtapi.connectorbay.com/mcp
RESTPOST https://byok-districtapi.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-districtapi.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your DistrictAPI key in the X-Upstream-Key header (get one at districtapi.dev).
  • Ask a question; the agent picks the right tool and answers from the live data.

District API connector: questions and answers

What is the District API connector?

District API (BYOK) lets an AI assistant read your own District API data through the District API API with a key you supply (DistrictAPI key). It is a hosted MCP server with 7 tools such as Lookup district, Get district, List district schools, Search districts, Find schools nearby, Get school, published by Unify Dynamics LLC. It is independent and not affiliated with District API.

How do I connect District API to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-districtapi.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-districtapi.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-districtapi.json.

Do I need a District API account or API key?

Yes: this is a bring-your-own-key connector. Create a DistrictAPI key at https://districtapi.dev/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is District API read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the District API connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Govee (BYOK)

Read your Govee devices and their state and change lights and plugs (power, brightness, color, color temperature) with your own Govee API key

Live · MCP + REST8 tools

Hostaway (BYOK)

Read your Hostaway vacation rental listings, reservations, calendars, guest conversations and reviews with an access token generated from your own account

Live · MCP + REST8 tools

Mashvisor (BYOK)

Read US city and neighborhood real estate market data from Mashvisor: for-sale listings, investment metrics, rental rates, Airbnb occupancy, schools and crime statistics, with your own API key

Live · MCP + REST12 tools

Phorest Europe (BYOK)

Read your Phorest salon branches, services, products, appointments, reviews and packages on the Europe server with your own API login

Live · MCP + REST10 tools

Phorest US (BYOK)

Read your Phorest salon branches, services, products, appointments, reviews and packages on the US server with your own API login

Live · MCP + REST10 tools

Rentcast (BYOK)

Look up US property records, value and rent estimates, sale and rental listings and ZIP-level market statistics with your own Rentcast key

Live · MCP + REST7 tools

Documentation

Back to top

District API (BYOK) — connector documentation

  • MCP endpoint: https://byok-districtapi.connectorbay.com/mcp
  • REST API: POST https://byok-districtapi.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-districtapi.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own District API DistrictAPI key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-districtapi.connectorbay.com/health · Tool schemas: https://byok-districtapi.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-districtapi · agent@connectorbay.com

What District API (BYOK) is for

District API (BYOK) lets an AI assistant read your own District API data through the District API API with a key you supply (DistrictAPI key). Read-only: 7 tools (lookup_district, get_district, list_district_schools, search_districts, find_schools_nearby, get_school, get_school_district). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.districtapi.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by District API. District API and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which school district covers 12865 Main St, Apple Valley, CA?"
  • "Show me the profile of school district 0600017"
  • "List the charter schools in district 0600017"
  • "Find school districts named Unified in California"
  • "Which schools are within 3 miles of 12865 Main St, Apple Valley, CA?"
  • "Show the profile of school 060001706027"

What it does

  • lookup_district: Find the school district that serves an address or a latitude/longitude, or fetch one by NCES id. Give exactly one of address, lat with lng, or nces_id. Returns name, grades, enrollment, finance and contact details.
  • get_district: Get the full profile of one school district by its seven-digit NCES LEA id: location, grades, enrollment, per-pupil spending and school count.
  • list_district_schools: List the open schools of a district, optionally only one school type or only charter schools. Returns name, grades, enrollment, coordinates and address.
  • search_districts: Search school districts by name, state or county (at least one is needed). Returns id, name, state, county, grades, enrollment and coordinates, with limit/offset paging.
  • find_schools_nearby: Find schools within a radius of an address or a latitude/longitude, with type, grades, enrollment and charter, magnet or virtual flags. Give an address or lat with lng.
  • get_school: Get the full profile of one school by its twelve-digit NCES school id.
  • get_school_district: Get the parent district of a school, given the school's twelve-digit NCES id.

BYOK key

You bring your own District API DistrictAPI key (https://districtapi.dev/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.districtapi.dev over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the District API API (api.districtapi.dev) with a BYOK key; documentation: https://districtapi.dev/docs. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by District API. District API and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your District API account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

District API (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What District API (BYOK) is. District API (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own District API data: Look up US school districts and schools by address, location or NCES id, with enrollment, grades and finance, using your own DistrictAPI key. You bring your own District API DistrictAPI key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one District API call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.districtapi.dev, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If District API rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What District API receives. The request we make on your behalf, including the key and the arguments, under District API's own terms and privacy policy. District API acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer District API gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your District API data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. District API (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at District API at any time to end all access.

Children. District API (BYOK) is a general-audience service operated by the adult using the assistant, under District API's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

District API (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the District API (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. District API (BYOK) provides: Look up US school districts and schools by address, location or NCES id, with enrollment, grades and finance, using your own DistrictAPI key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own District API credentials and only access data you are allowed to access. District API's terms apply to your use of District API; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by District API. District API and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data District API returns, lightly trimmed; it may be incomplete, delayed or changed by District API. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your District API account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent District API's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; District API may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your District API key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action District API takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-districtapi

District API (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. District API (BYOK) never asks for them.

Get District API (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own District API DistrictAPI key. Create one at https://districtapi.dev/, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to District API. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with District API.