Data & Storage · Integration
Bloomreach Discovery
Add Bloomreach Discovery to your product for your customers, and give your AI agents governed access to it.
Embed a Bloomreach Discovery integration so your customers can run search and recommendation queries against their own catalog and keep that catalog indexed from inside your product, with governed agent access to the same data. Catalog schemas differ per customer and change without notice, so attribute mapping is configuration rather than a release on your side. fastn handles per-tenant credentials, pagination, and throttling on large indexing runs.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers run product search queries against their own Bloomreach Discovery catalog from inside your product.
Read recommendation and related-item results so your product can surface them in its own interface.
Push catalog updates for indexing so search results reflect the customer's current attributes and availability.
Read search performance signals such as top queries and zero-result queries for reporting in your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a catalog search to ground an answer in the customer's own product data.
An agent reviews zero-result queries and proposes catalog or synonym fixes.
An agent reacts to a completed indexing run and reports which items failed to index.
Example prompt
Show the top search queries from last week that returned no results and how often each was searched.
Set up Bloomreach Discovery in 4 steps
- 01Open the Bloomreach Discovery connector from your fastn dashboard.
- 02Have each customer authenticate their own Bloomreach account and select the catalog to query.
- 03Map their catalog attributes to your product's schema, then enable queries and indexing actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Bloomreach Discovery integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Bloomreach Discovery integration without building it. Your customers connect their own Bloomreach Discovery account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Bloomreach Discovery update is not your on-call problem.
- One integration serves your product and your agents. The same governed Bloomreach Discovery connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Bonsai ElasticsearchWorks well with
Bloomreach Content
ShopifyOften used alongside
Tools the same teams tend to run next to Bloomreach Discovery, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceBloomreach Discovery integration FAQ
How do I add a Bloomreach Discovery integration to my product?
Enable the Bloomreach Discovery connector in your fastn dashboard, then let each customer authenticate their own Bloomreach Discovery account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Bloomreach Discovery client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Bloomreach Discovery account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Bloomreach Discovery account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Bloomreach Discovery integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent runs a catalog search to ground an answer in the customer's own product data.
Who maintains the Bloomreach Discovery integration?
fastn does. When Bloomreach Discovery changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Bloomreach Discovery integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Bloomreach Discovery reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Bloomreach Discovery integration?
A common starting point: run product search queries against their own Bloomreach Discovery catalog from inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Bloomreach Discovery integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Bloomreach Discovery does not change your per-connector cost. You can start free with 3 connected accounts.
Add Bloomreach Discovery to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.