Connect any API.
No connector required.
Every other platform makes you wait for a connector to exist. Spojit doesn't. Paste a request, link the docs, or just name the vendor. Miraxa searches out the documentation and builds an authenticated, typed node in seconds. The integration you need is never on a roadmap.
curl -X POST \
https://api.harborline.io/v3/consignments \
-H "Authorization: Bearer hl_live_••••" \
-d '{
"reference": "SO-48213",
"service": "express",
"destination": { "postcode": "2000", "country": "AU" },
"parcels": [{ "weight_kg": 2.4 }]
}'referenceservicestandard · expressdestination.postcodeparcels[].weight_kgconsignment_idtracking_urllabel_pdfFrom a vendor name to a working node
Point Miraxa at the API
Paste a cURL or a sample payload, link the vendor docs, or just name the tool. Miraxa can search out the documentation itself. No connector has to exist.
Miraxa reads and builds
It works out the endpoint, the auth scheme, and the request and response shapes, then generates a typed node with inputs and structured output.
Use it like any other node
Drop it into a workflow, map fields into it, branch on its output. Agents can call it as a tool. Save it and reuse it across workflows.
A real node, not a raw HTTP box
No connector required
The integration you need is never stuck on a roadmap. Any REST API works the moment you have a request or a docs link, not when we get around to building it.
Finds and reads the docs
No docs link handy? Miraxa searches the web for the API reference, then reads the endpoints, parameters, and auth for you. No translating docs into config by hand.
Paste a request or payload
Already have a working cURL or an example response? Paste it. Miraxa infers the shape and builds the node around exactly what you gave it.
Auth, detected and handled
API keys, bearer tokens, basic auth, OAuth. Miraxa spots the scheme and wires it up. Secrets are stored encrypted, never in the workflow definition.
Typed inputs and output
The generated node has real, typed fields. Map data into it with confidence and read structured output into the next step. No blind string juggling.
Instantly agent-callable
Every node you build this way becomes a tool your AI agents can call, with the schema they need to use it correctly already attached.
Wherever the catalog runs out
That niche regional vendor
The 3PL, ERP, or payments provider nobody else integrates. If it has an API, Miraxa builds the node, so a long tail of tools is no longer a dealbreaker.
Internal and legacy APIs
Your own services and the in-house systems no SaaS will ever ship a connector for. Paste an endpoint and put them in a workflow today.
Brand-new APIs
A tool that launched last week, or a beta endpoint. You do not wait for connector support. Point Miraxa at the docs and go.
One-off endpoints
A single webhook callback or a one-call lookup that never warranted a full connector. Build just the node you need, nothing more.
Build it now, or wait for a roadmap
The connector catalog is a head start, not a ceiling. When your tool isn't in it, you build the node anyway.
The Spojit way
- The API you need has no pre-built connector, and you do not want to wait
- You have a working request, a sample payload, or a link to the docs
- You want a typed node with auth handled, not a raw HTTP box to wire by hand
Everywhere else
- Search the connector catalog and hope your tool is in it
- Request it, then wait for a vendor roadmap you do not control
- Fall back to a raw HTTP step and hand-configure every header and field
If it has an API, you can connect it
Start free, paste your first request, and watch Miraxa turn it into a node. No card needed.