Xtrable
The API is the part of your architecture the outside world actually touches, so it is the part that most needs to stay honest. In NeoArc, your contracts are projections of the same model as everything else, which means they are documented, traceable and consistent by construction.
Schemas: one shape, many renderings
A schema is a reusable data shape, a request body, a response, a payload, authored once and shared by every endpoint that needs it. You define the shape, and NeoArc renders it as a JSON contract or an XML contract from the same definition. Schemas compose and reference each other, including generic shapes like a paged envelope, so you describe a structure once and reuse it everywhere.
REST and GraphQL, both shipped
NeoArc gives you both of the contract styles teams build on today. Design REST operations with methods, tokenised paths, parameters, request and response bodies, environments, versioning and auth. Design GraphQL alongside it. Both are first-class, so you can model the surface your consumers actually call rather than bending everything into one shape.
Every value traces home
Wire a path segment, a header, a query parameter or a response field to the model, and NeoArc carries the lineage all the way down: an API value traces through the schema, through the database, to the model property it originated from. Classify a field as sensitive once on the model, and that classification appears on every API that exposes it, automatically.
OpenAPI in and out
- Import an existing OpenAPI or Swagger document and NeoArc turns it into a model you can reason about, keeping cross-references as real relationships.
- Export your authored API back to a valid OpenAPI document, ready to feed the mocks, SDKs and docs your delivery pipeline already generates.
Your contract and your model are never two separate things drifting apart. They are one design, published in whatever form a consumer needs.