Connect any API
by asking.
Tell lynox "connect my CRM" — or any tool. It finds the docs, extracts a typed profile, and reuses it in every chat. Where a custom app or API key is needed, it walks you through the extended setup.
How it works
Three steps,
one ask.
-
Tell lynox what to connect
"Connect my CRM." "I want to talk to my billing tool." "Connect this internal microservice." Natural language — no plugin marketplace, no SDK install. lynox finds the docs (or asks you for them) and reads the schema.
-
lynox extracts the profile
A small fast LLM (Haiku, Mistral Small, or whatever you've configured) reads the docs and extracts an api_setup profile — endpoints, auth scheme (Bearer / API-key / OAuth), required params, response shapes. You audit it before it goes live.
-
Typed methods, reusable forever
The profile compiles to a typed v2 schema lynox can call from any thread. Every future chat gets the same methods. If a custom app, API key, or OAuth callback is required, lynox surfaces the extended-setup steps right there.
Honest scope
What works today —
what's on the roadmap.
Today
- Bearer-token APIs (most REST APIs) — typically 90 seconds end-to-end
- API-key headers (X-API-Key, custom headers)
- Query-parameter auth
- Public no-auth APIs
- Schema extraction from any HTML or OpenAPI docs
- Extended-setup guidance for custom apps / personal access tokens
On the roadmap
- OAuth 2.0 Authorization-Code callbacks (need per-tenant webhook URL — coming with PRD-WEBHOOK-RECEIVER)
- OpenAPI/Swagger spec import (faster than docs scrape)
- GraphQL endpoint introspection
- Per-thread API result reuse within the conversation
You describe the API — lynox reads the docs and builds the integration.
One ask,
every API.
Try it on any tool you've been meaning to connect — lynox does the docs-reading.