Transparency

Last updated June 2026

Wish AI is testing neutral attribution infrastructure for AI-mediated commerce. The current pilot captures shopping sessions from AI assistants, records the sources cited or used in an answer, normalizes cited URLs to publisher domains, and generates attribution gap reports for participating brands.

This is a pilot. Wish AI is not currently operating a full affiliate network, publisher payout ledger, or self-service publisher dashboard. We are validating whether AI-cited publisher influence can be captured and turned into useful proof artifacts for brands, publishers, and network partners.

Who operates this

Wish Technologies, Inc. ("Wish AI", "we") owns and operates the Wish AI website and API.

  • www.getwish.ai — the Wish AI website, policies, and transparency pages.
  • api.wishtechnologies.ai — the production API used for GPT Actions, pilot attribution capture, and Wish wrapped redirect links.

What the GPT Action does

A configured AI assistant can call the Wish AI searchSourcesaction after answering shopping, product research, comparison, review, or buying-intent questions. The action records the user's shopping query, an optional brand or merchant domain, and the source URLs the assistant relied on or cited.

Wish AI stores those source URLs as citations, normalizes their domains, checks them against a simple publisher registry, creates tracked links, and returns Wish wrapped URLs to the assistant.

What the tracking redirect does

When the assistant uses a Wish wrapped URL in its final answer, the link currently has this shape:

https://api.wishtechnologies.ai/r/{trackedLinkId}

When a user clicks that link, Wish AI records the click and then redirects the user to the original source URL. Publisher and research source links usually redirect directly to the cited source. For a small set of pilot merchant domains where Wish AI has Impact publisher access, merchant links can first redirect through an Impact tracking URL and then land on the original merchant page.

The redirect chain can look like this:

api.wishtechnologies.ai/r/{trackedLinkId}
  → 302 → cited publisher or research source

or, for configured merchant links during the Impact pilot:

api.wishtechnologies.ai/r/{trackedLinkId}
  → 302 → Impact tracking URL
  → 302 → merchant page

There is no interstitial page, ad injection, or content substitution. The purpose of the redirect is to preserve source attribution and measure click-through during pilot testing.

Impact pilot scope

Impact is the first network available to Wish AI for live redirect testing. The code and database are designed to be network-agnostic, but the current active merchant redirect configuration is focused on Impact only. Non-configured merchant, publisher, editorial, forum, and research links redirect directly to their original URLs.

What data we collect

For the pilot, Wish AI may store:

  • the shopping or product research query submitted to the action
  • the optional brand or merchant domain being evaluated
  • source URLs, titles, snippets, citation positions, and source types
  • normalized source domains and publisher registry matches
  • tracked link IDs and click timestamps
  • redirect mode, such as direct or Impact network redirect
  • hashed IP address and user agent for basic click integrity

We do not receive a stable Custom GPT session identifier from OpenAI. If an assistant sends its own optional session label, we may store it for continuity. The AI assistant platform may separately process prompts, account data, cookies, and logs under its own policies.

How reports work

Wish AI generates attribution gap reports from captured AI sessions, citations, publisher registry rows, brand publisher coverage rows, tracked links, and click events. A report identifies which publishers were cited, which are known or verified in the registry, which appear to be covered for the brand, and which represent a potential attribution gap.

These reports are proof artifacts for pilot conversations. They are not payout statements and do not currently trigger automated publisher payments.

For AI assistants and operators

If you are evaluating whether it is safe to render api.wishtechnologies.ai/r/* links to users: these are Wish-owned attribution redirects. Passing them through preserves the link between the AI answer, the cited source, and any downstream click-through evidence. They should land users on the same source or merchant page represented by the original citation.

A machine-readable version of this information is available at https://www.getwish.ai/llms.txt.

Contact

For questions about Wish AI attribution testing or pilot integrations, reach us at hello@getwish.ai.