Register as a service provider at edexchange.pesc.org, complete onboarding to receive your service provider credentials, and add the sending institution to your logical group in the EdExchange directory.
Query the EdExchange directory API to resolve the receiving institution's endpoint: GET /api/v1/endpoints?institutionId=<receiver_id>&documentType=Transcript&format=PESCXML to retrieve the target endpoint URL and supported formats.
Build the PESC XML transcript document conforming to the PESC CollegeTranscript XML schema (v1.9 or later); validate locally against the published XSD before transmission.
Sign the document digitally if the receiving endpoint requires a signature; upload both the XML file and the signature file as parts in a multipart/form-data POST to the resolved endpoint URL.
In the POST body include the required metadata parameters (sender ID, receiver ID, document type, document format); the API returns a transaction ID on success.
Poll the EdExchange transaction status endpoint using the returned transaction ID to confirm delivery acknowledgment from the receiving institution.
Known gotchas
The EdExchange directory resolves endpoints dynamically; cache the endpoint URL no longer than your session since institutions can change endpoints or formats between requests.
PESC XML schema versions (e.g., v1.9 vs v1.10) are not backward compatible in strict validation; confirm the exact schema version the receiving institution's endpoint accepts before generating the document.
Digital signature requirements vary by institution; some endpoints reject unsigned documents and return a 4xx with no body — check the endpoint's metadata flags in the directory response for the requiresSignature field.
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