CoreModelsGuides
Synapse
Record the constraints that die on the way to a registered schema.
- From JSON Schema to a Registration-Ready Synapse Schema in One CallQuickstart · You have a JSON Schema. Synapse — Sage Bionetworks' data platform — will not accept all of it. Registered Synapse schemas are draft-07, and not even all of draft-07: the platform's JsonSchema REST object models a specific keyword subset, and anything outside it simply is not part of a registered schema. This quickstart takes a small, real schema across that boundary in one HTTP call to CoreModels (by ARAMAI), then reads the machine-readable ledger of exactly what the boundary cost.
- The Synapse Export, Route by Route: A CoreModels API ReferenceAPI · Every format in the CoreModels transform surface belongs to two lists — the formats we decode and the formats we encode — and synapse appears in exactly one of them. The decode list is jsonschema | shex | avro | jsonld | sql | osi | osi-json | owl | linkml | protobuf | odcs | odm; the encode list swaps odm out and synapse in. This page is the working reference for that one direction: which routes produce a Synapse-ready schema, what each accepts, which one controls the registered-schema $id, and how to bring a Synapse schema back in anyway.
- Synapse Schemas from an Agent: transform_schema over MCP, End to EndMCP · Connect an MCP client — Claude Desktop, an IDE agent, your own orchestration — to a CoreModels deployment at https://go.coremodels.io/mcp (OAuth-protected), and two tools give it the entire Synapse workflow: transform_schema produces the registration-ready draft-07 schema, and generate_synapse_manifests produces the tabular curation companions. This article is the end-to-end session, with exact arguments and exact results, so an agent — or the person supervising one — knows precisely what each call does and does not do.
- Automating Synapse Schema Releases: Determinism, Plan Replay, and Version DisciplineAutomation · Run the same Synapse export twice against the same model and you get the same bytes. That single property — deterministic encoding — is what turns the CoreModels synapse profile from a converter into release machinery: outputs you can commit and diff, plans you can store and replay, and a version rule you can enforce mechanically instead of remembering. This article builds that pipeline piece by piece, with the honest constraints stated where they bite.
- Inside the synapse Coder: The Whitelist, the Ledger, and the Edge CasesDeep dive · The entire CoreModels synapse profile can be stated in one sentence: *encode the neutral model as JSON Schema, then keep only what the Synapse JsonSchema REST object has a field for — and write down every single thing that rule removes.* This deep dive unpacks that sentence into the parts an integrator eventually needs: the IR-to-output mapping, the exact keyword whitelist and how strips are classified, the extras channel that carries verbatim keywords through the neutral model, the complete inventory of lossiness records the encoder can emit, and the edge cases our test suite pins — including the ones where we deliberately refuse to guess.
Start building
14-day free trial. Builder $49/mo after the trial. Cancel any time.