/ partners · resources
What you can use today,and what is not built yet.
Everything a partner needs to evaluate Inferrex is already public — the documentation, the developer surfaces and the corpus itself. The partner-only material is honestly still being written.
/ available
All of it public, none of it gated.
Documentation
The full developer documentation, including quickstart. No partner login and no gate.
ReadInferrexAPI, InferrexSDK, InferrexMCP, InferrexCLI
The four programmable surfaces, with reference material for each.
API referenceThe Corpus
What Inferrex has comprehended: 1,941+ providers fully specified across 234,373 vendors catalogued. Check your customers' systems against it before a conversation.
ExploreThe Universe
The same coverage, drawn. Useful in front of a customer who wants to see whether their stack is understood.
ExploreInsights
The long-form argument for comprehension over connection, which is usually the harder half of a partner conversation.
ReadDevelopment environment
Self-directed and needs no conversation. The fastest way to answer a customer's question is to point Inferrex at their API.
Start/ honestly
Named so you can ask, rather than discover.
There is no partner portal, no certification programme, no deal registration system and no partner-only enablement library. Each of those is a real thing to build and none of them exists today.
Saying so is more useful than a page implying otherwise. A partner who plans around a portal that is coming soon has been misled; a partner who knows the arrangement is currently a direct conversation can decide whether that works for them.
What replaces them for now
/ preparation
Three things worth doing first.
Name the model
Build, Embed, Operate or Refer. Most partner conversations stall because this was assumed rather than agreed.
The four modelsCheck the coverage
Look up your customers' systems in the corpus. It is the fastest way to know whether this is useful to you.
ExploreTry it on something real
Point it at an API you have had trouble with. Nothing about that requires a conversation first.
StartBring a customer problem rather than a partnership template.
The useful first conversation is about one estate you are already trying to help, not about the shape of an agreement.