/ contribute
Submit an API.Everyone gets it.
An API you need comprehended may not be in the corpus yet. Submit its public specification and it enters the same pipeline as everything else.
/ what happens
Submit → Infer → Review → Publish → Available to everyone.
Submit
You give us a public URL for the specification.
Infer
Inferrex parses it, resolves entities and fields, classifies each field by meaning, and relates it to the canonical model.
Review
A person checks the result before it goes anywhere. Nothing publishes unreviewed.
Publish
The entry ships in a versioned release, carrying its provenance: crawled, vendor-submitted, or improved by a named contributor.
Available to everyone
Once published, the comprehension is in the corpus for every Inferrex user. Coverage is not a per-customer asset.
/ what we accept
A publicly reachable URL for a specification. That is all.
The submission gate rejects, automatically:
- Anything requiring credentials
- URLs returning 401 or 403
- URLs redirecting to a sign-in page
- Addresses on private networks
The check is deterministic, and it runs before anything is fetched. If a specification is not public, Inferrex will not take it.
We do not accept file uploads
/ if you are the vendor
Submissions from the organisation that publishes the API carry further.
A vendor-confirmed entry earns Vendor Verified status, the highest in the corpus, and vendors can correct comprehension of their own APIs directly.
Vendor corrections reach the map on the nightly rebuild. Published figures update on a separate reviewed cycle.
/ what you get back
Acknowledged, then told when it publishes.
If you asked to be credited, the entry carries your name as its contributor.