Your own systems
Query the internal API nobody outside your team knows how to use, in plain language.
Tools
Connect any API. Then just ask for it.
Most assistants can only reach the tools their vendor chose to ship. Sigma Domain works the other way round: you bring the API, and it becomes something you use by describing what you want.
- Your internal API
- Data you license
- Marketplace tools
One conversation that can use all of them
How it works
You connect it once. After that, you talk.
Point Sigma Domain at an endpoint — your company's internal service, a data provider you pay for, a SaaS product you already use. It reads the specification, works out the parameters and handles the authentication.
From then on there's no syntax to remember and no prompt formula to get right. If you'd describe the task to a colleague in a sentence, that sentence is the interface. The assistant is Claude, which matters most exactly where naive tool-calling breaks: work that takes several steps, needs a judgement call in the middle, or requires noticing the first result was wrong.
Data you already pay for
Property records, enrichment, mapping, search — if you have a key, you can use it without writing another integration.
Second opinions
Put the same question to ~70 other models across ~20 providers via Amazon Bedrock and compare the answers side by side.
Cost
What a tool call costs you
Calls are metered against your plan. Guests and free accounts get a daily allowance; Standard raises it and lets you keep going on a pay-as-you-go basis. Tools published by other people can carry their own per-call price, always shown before the tool runs.
Your own
Adding a tool takes about a minute
You don't need to ask us, and you don't need to move your API anywhere — host it wherever you like and Sigma Domain calls it.
The quickest route is to say so in a conversation: "import the API at https://your-service.com/openapi.json". It reads the docs and registers every endpoint as a tool. For a single endpoint, or an API without public docs, open Toolkit → + Add Tool and paste a spec, JSDoc'd code, or a description. Either way it's live immediately and attributed to you — and you can charge per call for it.
One thing to know: tools added this way are public and callable by anyone, including guests. There's no visibility control in that flow yet, so don't register an endpoint you need kept private.