Review the SEA's published extension schema (usually an XSD or JSON Schema file) to identify the new element names, types, and associations with core Ed-Fi entities such as StudentSchoolAssociation.
In your local MetaEd project, create a new Domain Entity Extension that references the core entity and adds the custom element; run the MetaEd build to generate the extension SQL and API surface scripts.
Apply the generated scripts to your ODS database and redeploy the Ed-Fi ODS/API so the extended endpoints (e.g., /ed-fi/studentSchoolAssociations with an _ext block) are live.
Submit extension data by nesting values inside the _ext object in POST/PUT request bodies, keyed by the extension namespace assigned by the SEA.
Validate using Swagger UI at /metadata/data/v3/swagger.json to confirm the extended schema is visible, and run a test POST to verify the extension fields are stored.
Document the extension namespace and version so downstream consumers (dashboards, state extract jobs) can reference the correct _ext path.
Known gotchas
Extension namespaces must be unique; using the default 'EXTENSION' namespace in production causes collisions when multiple vendors share an ODS.
MetaEd version must match the target ODS/API Data Standard version (e.g., DS 5.x requires MetaEd 4.x); mismatched versions generate incompatible SQL artifacts.
Extensions applied to one school year's ODS are not automatically forward-carried; plan migration scripts when the SEA upgrades the ODS/API version.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp