# Your data. Better connected. > You maintain the data. We’re building a way for AI assistants and agents to reach it, on terms we agree together. We’re exploring early pilots: one dataset or API, agreed cases, a small trial. - URL: https://ikag.dev/partners - Status: We’re talking with data and API providers now. IKAG’s first capability covers company legal identity from official registries. - Updated: 2026-10-17 ## Your data, in every AI people already use. People ask ChatGPT, Claude, Gemini, Cursor and their agents for data none of them have. IKAG is how those requests reach you, as paid calls. - **New customers, through AI.** Requests from people using the AI apps they already have become paid calls to you, from people who have never signed up for your product. - **Free distribution.** There’s no fee to be listed. IKAG puts your data in front of the AI apps people already use, and you’re paid per call, on terms we agree together. - **One integration, every AI app.** Any AI app that speaks MCP can reach you through IKAG, so there’s no plugin, app or MCP server to build and keep up for each one. - **We build the adapter.** IKAG builds and maintains the integration with your API, within your rate limits and terms. You share documentation and test access. - **Paid per call, metered.** Every call is metered and settled on agreed terms, and we share the numbers with you, so you see exactly what was used. - **Your terms come first.** Data use, caching, retention, redistribution and attribution are agreed in writing before anything is built. - **Your source travels with it.** Each value from you carries your source details wherever IKAG returns it. - **No billing or support to run.** IKAG takes care of the people asking: sign-in, a quote before each paid call, spending limits and billing. You answer the calls. Start small: one dataset or API, agreed cases and a shared report. [What a pilot involves](https://ikag.dev/partners#pilot). ## How a call would reach a partner How a call would reach a partner, once agreed. Simplified. 1. **An agent asks.** A question arrives from an assistant, an agent or an app. 2. **IKAG chooses a source.** When your data fits the request and the terms allow it, the call comes to you. 3. **Your API answers.** Through an adapter we build and maintain, within your limits. 4. **Your attribution travels with it.** Each value from you carries your source details. Every call is metered. ## An early pilot, in plain terms A pilot is small on purpose: one dataset or API, agreed cases, a fixed period, and a shared report. Either side can stop at any point. ### What we’re looking for - Data that people ask AI about: official records, company data, listings, jobs and other specialist datasets - A documented API, or files we can serve reliably - A licence that can allow use by AI assistants and agents, as agreed ### What we’d ask of you - Documentation and a technical contact - Test access on terms you set - Your rules on rate limits, caching, retention and attribution ### What IKAG would do - Build and maintain the adapter to your API - Respect your limits and terms on every call - Return your attribution and source details with each value from you - Meter every call and share the numbers with you ### What the pilot would measure - Coverage and quality on cases we agree in advance - Latency, errors and cost per call - Whether attribution works the way you need - Whether both sides want to go further ## Three ways to work together ### Managed integration IKAG would run the connection and offer your data to people using IKAG. - Who calls you: IKAG, for its users - Settlement: Per call, on agreed terms ### Bring your own key Your customers use their own accounts with you, through IKAG. - Who calls you: Your customer, via IKAG - Settlement: Their existing plan with you ### Open data Public or openly licensed data, used within its licence. - Who calls you: IKAG, within your licence - Settlement: As your licence allows How each model is priced and settled is agreed with each partner. Nothing here is an offer. ## How a pilot would come together 1. **Introduction.** You tell us about your data, how it’s accessed and licensed. 2. **Fit and terms.** We review your API, limits and licence, and the model that suits you. 3. **Written agreement.** Test access, data use, retention, attribution and pricing, agreed in writing. 4. **Build and test.** We build the adapter under the agreed test access. 5. **Monitored pilot.** A small trial on the agreed cases, then a shared report. 6. **Decide together.** Wider use only if both sides choose to go ahead. ## Straight answers ### Are you working with data partners now? Yes. We’re talking with data and API providers now about early pilots. IKAG is opening to early users and data partners first. Its first capability, company legal identity from official registries, already runs inside IKAG, and early partners help shape what comes next. ### What does a pilot involve? A small, bounded trial on agreed terms: we review your API and licence, agree test access and data use in writing, build and maintain the adapter, run a monitored trial on agreed cases, and share what we measured. Either side can stop at any point. ### Will you integrate before we agree terms? No. Test access, data use, retention, caching, redistribution, benchmarking and attribution are agreed in writing before any integration that needs them. Nothing is resold or published without that agreement. ### Do we need to build anything? Usually not. If you have an API, we would build and maintain the adapter. We would ask for documentation, agreed test access and a technical contact. ### Are commercial terms already set? No. Pricing, attribution, usage limits and any resale rights are agreed with each partner. Nothing on this page is an offer. ### Who owns the customer relationship? With your own keys, customers keep their account with you. With a managed integration, it is part of the terms we agree. ### Will answers credit our data? In a pilot, IKAG would return attribution and source details with every value that comes from you, in the form we agree. How an assistant or app then displays them is up to that assistant or app, so we cannot promise it is shown. ### Will you compare our data with other providers? IKAG is being built to evaluate sources so it can choose between them. Publishing any comparison that names you needs your agreement first. ## Tell us what you offer. Four short required fields. If there’s a fit, we’ll suggest a first call about a pilot. 1. We look at your note and the data you describe. 2. If there’s a fit, we reply to suggest a first call. 3. Nothing is agreed until we both sign. Enquire at https://ikag.dev/partners#enquiry.