onticfabric.ai — Ontic Fabric Gateway

Endpoints

Path	Method	Purpose	Status
`/v0/leads`	`POST`	Submit a pilot, pricing, or community access request.	live
`/v0/traffic`	`POST`	Ingest page traffic classification from Ontic Fabric websites.	service
`/v0/ontologies`	`GET`	List public ontology cartridges and compatibility metadata.	planned
`/v0/ontologies/{id}`	`GET`	Fetch a cartridge manifest, primitive types, edge types, and markers.	planned
`/v0/inference`	`POST`	Route an inference request through substrate policy.	planned

Endpoint status describes the public gateway surface, not every internal service. Do not infer public availability from internal deployments.

Surface model

Filesystem first

Linux agents use ordinary POSIX/9P semantics where available.

Gateway second

HTTP serves clients that cannot mount or speak substrate RPC.

Typed cartridges

Domain schemas and edge semantics are declarative configuration.

Provenance

Claims, files, edges, and work outcomes retain source lineage.

Cartridge index

Ontology ID	Domain
`sys:software-v1`	Composite software domain: code entities plus work graph, with cross-domain tracking edges.
`sys:work-graph-v1`	Tasks, milestones, dependency DAGs, state transitions, and review evidence.
`sys:famix-v2`	Software architecture and code dependency primitives.
`sys:hohfeldian-v1`	Legal rights, duties, parties, filings, contracts, and evidence routing.
`sys:commerce-v1`	Commerce observations, products, merchants, pricing, and review payloads.
`sys:infrastructure-v2`	Infrastructure resources, deployment state, and operational topology.
`sys:travel-v1`	Trips, bookings, routes, locations, and travel evidence.

Cartridge availability may differ between Community Edition, internal deployments, and managed workflows. A public registry manifest will carry versions and compatibility ranges.

Machine-readable index

A current static index is available at /index.json.

GET /index.json

{
  "service": "ontic-fabric-gateway",
  "version": 0,
  "endpoints": [
    { "path": "/v0/leads", "method": "POST", "status": "live" },
    { "path": "/v0/traffic", "method": "POST", "status": "service" }
  ]
}

Client guidance

Do not retry non-idempotent lead submissions indefinitely.
Treat 4xx as a contract error; inspect the response body before retrying.
Use the future cartridge registry for schema discovery instead of hardcoding internal ids.
Preserve human-submitted identifiers and source metadata; do not synthesize leads.