The operator
idclinktech is an independent inference gateway run by a small team of infrastructure engineers. No lab of our own, no model to sell you, no stake in which one you pick.
SEC.01 — POSITION
The first wave of AI products was built on one provider, one model, one API. That worked while there was a clear leader. It does not work now: three or four frontier labs trade the top spot every quarter, and the open-weight flagships keep closing the gap behind them.
Teams that bet on a single provider spend engineering quarters writing adapters, hedging against quota cuts, and explaining surprise invoices to finance. idclinktech absorbs that work: one endpoint, one schema, one contract, across every model worth shipping.
We are independent on purpose. There is no model of ours to route you toward, so there is nothing to gain from favouring a brand. If the cheapest open-weight model is the right answer, we say so. If the answer is paying ten times more for the frontier tier, we say that too.
FIG.01 — OPERATOR IDENTITY BLOCK
| Entity | idclinktech, Inc. — Delaware, USA |
| Founded | 2023, spun out 2024 — customer-funded ever since |
| Models trained | None. By design — we operate the layer, not the lab |
| Catalog | 36 models across 13 providers, updated on upstream ship day |
| Routed regions | 4 worldwide, pinnable on Scale and above |
| Endpoint uptime | 99.95% trailing 90 days, against a written SLA |
| Support path | One inbox, answered by the engineers on call |
| Contact | sales@idclinktech.com, read the same business day |
FIG.02 — ROUTED TOPOLOGY
SEC.02 — OPERATING PRINCIPLES
Printed on the outside of the box rather than buried in an internal handbook, because a principle nobody can audit is a slogan.
We take no revenue share from any upstream lab, and no model earns preferential routing for commercial reasons. The recommendation you get is the one we would make for our own workload, with the same trade-offs and the same uncertainty attached.
Infrastructure should disappear into the background. We optimize for predictable latency, deterministic error semantics, and routing decisions that fit in one sentence — not for a hero number in a launch post.
Rates are quoted per workload and locked for the term. Route, provider latency, and the rate applied come back on every response in X-IDC-* headers. Traces export to your own stack; there is no dashboard you are required to live in.
We hire slowly and ship slowly on purpose. The product is a contract: the model keeps working, the bill makes sense, the rate is the rate. Holding that line takes patience rather than headcount.
SEC.03 — REVISION HISTORY
The company changed shape three times. The thing it does — keep somebody else's model reachable — has not changed since the first internal build.
| Rev | Year | Stage | What changed |
|---|---|---|---|
| Rev A | 2023 | Internal routing layer | Written because three teams inside one company were re-implementing the same provider-failover logic in three languages. The tool worked. It was never the product. |
| Rev B | 2024 | Spun out to first customers | idclinktech, Inc. incorporated in Delaware. Six design partners signed in the first quarter, every one already running two or more providers and tired of maintaining the seam. |
| Rev C | 2025 | Multi-region, multi-tier capacity | Routed regions reached four. Dedicated capacity went generally available. Open-weight flagships joined the catalog on the same schema and the same contract as the closed frontier. |
| Rev D | 2026 | Current sheet | Thirty-six models from thirteen providers, four capacity tiers, public pricing, a written SLA. Still independent, still customer-funded, still answering sales mail ourselves. |
REV D is the current sheet · superseded revisions retained for traceability
Read the changelogSEC.04 — CONTACT SCHEDULE
Conversations are not gated behind a multi-step form. Send a sentence or two about what you are building; every message is read by a person.
Quotes, trials, contracts. Send your model mix, expected monthly tokens, target regions, and any compliance constraints; a trial key and a pricing sheet for that shape usually come back within one business day. sales@idclinktech.com
Routing behaviour, schema edges, observability. Same inbox: sales reads it first and hands anything technical to the on-call engineer. We do not run a separate support queue at our size, and we prefer it that way. sales@idclinktech.com
SOC 2 Type II reports, sample DPAs, subprocessor lists, and architecture diagrams go out under mutual NDA — include your review timeline. The short version is already published on the security sheet.
We hire rarely, and only for roles that already have work waiting. There are no open listings today; a note describing what you would fix will still be read. Press questions go to the same address.
SEC.05 — COMMISSIONING
No discovery call script, no SDR relay. Tell us the workload and an engineer answers.