ForkTex Intelligence — One API for AI Capability
Romania
A capability-first AI platform: consumers ask for extraction, retrieval or transcription and never name a provider, so the provider can change without a rewrite.
- Client
- ForkTex
- Industry
- Artificial Intelligence
- Period
- Jan 2025 — Ongoing
Outcomes
- Providers
- Anthropic and OpenAI, interchangeable
- Surface
- Typed API, SDKs, MCP tools
The situation
AI capability changes faster than the systems using it. A service that names a provider in its code has bound itself to that provider’s model lineup, pricing and availability.
What we built
Capability surface
A typed API over chat with streaming and structured output, embeddings, document extraction, audio and video transcription, retrieval, and usage accounting. A consumer asks for extraction against a schema, not for a named model from a named vendor.
Retrieval
Self-hosted Qdrant with optional CLIP multimodal embeddings. Retrieval quality determines whether a system like this is useful, and outsourcing it makes it the part you can least influence.
Agent surface
The same route table projected through MCP, so tools and the HTTP API cannot drift — there is one implementation.
What mattered
Structured output is what makes this usable outside a demo. A free-text response needs parsing, and parsing free text is where reliability goes. A response validated against a declared schema either conforms or fails loudly.
Outcome
In production behind our own systems and client deliveries, with Anthropic and OpenAI interchangeable behind one contract.