APIs
Useful where current availability, pricing or eligibility data needs a live source. Authentication and permitted fields stay within the provider's rules.
Put your product inside useful AI workflows, without giving up checkout.
InvokeForge builds focused discovery, comparison and referral tools for AI assistants. We use provider approved data and handoff methods, then let the user choose whether to continue to the provider.
User initiatedNo automatic referral clicks
Provider hostedCheckout remains with you
Rights validatedProgramme approval is not assumed
Structured attributionChannel separation where supported
The model
Help first. Handoff second.
The commercial path should be a continuation of a useful answer. InvokeForge is designed to perform the comparison or assessment work before asking the user to leave the assistant.
01
User asks
A real task begins inside an AI assistant, such as finding a suitable eSIM, ground transport option or post disruption next step.
02
InvokeForge helps
The tool structures the request and uses approved information to produce a relevant result.
03
Provider appears when useful
If your product is a legitimate fit, it can be shown as an optional continuation path with the commercial relationship disclosed where appropriate.
04
User completes with you
The user chooses the link and completes the transaction, booking or claim flow on the provider's own service.
Integration options
Use the strongest approved source you can provide.
Different categories need different levels of freshness. We can adapt to the provider's approved integration model rather than forcing every partner into the same technical shape.
Product feeds
Useful for structured catalogues, route tables, plan data and other information that can tolerate the provider's stated refresh cadence.
Deeplinks
Useful for sending a user directly to a relevant provider page after the assistant has already done the comparison work.
Affiliate attribution
Useful where a standard user clicked referral is permitted. We can separate channels such as ChatGPT, Claude, Muse or Grok where the programme supports that attribution.
What we need from partners
Clear rights matter as much as good data.
- Permission for the actual AI assistant distribution workflow
- A defined source for product, price, route, eligibility or offer data
- A stable user initiated handoff method
- Clear disclosure, branding and attribution requirements
- Any restrictions on channels, paid media, software, sub affiliates or automated systems
What we do not assume
Affiliate availability is not blanket permission.
InvokeForge distinguishes between being able to join a programme and being allowed to use that programme inside an AI assistant product. Where terms are missing, generic or ambiguous, we keep the provider out of production until the rights are clear.
Current validation examples
Evidence before expansion.
Our first provider relationships are intentionally narrow. These examples demonstrate the operating model without implying broader market coverage than we have.
AirHelp / FlightClaim
AirHelp has approved the affiliate relationship and confirmed that user clicked AI origin referrals can work under programme conditions. FlightClaim preserves an official self claim route and does not auto click or submit a claim.
Omio / Ground Transport Finder
Omio has confirmed that user initiated referrals using approved product feeds and deeplinks may be used in ChatGPT, Claude, Muse and Grok. Its currently available feed data is not real time, so route and price information must be labelled accordingly.
Interested in an AI native distribution test?
Send the programme, data source and any channel restrictions you want us to evaluate. We will keep the proposed workflow narrow and explicit.