The merchant,
from the descriptor.
Turn 'SQ *BLUE BOTTLE 4471' into Blue Bottle Coffee, with a logo, a category, and a website — built for neobanks and expense tools.
Resolve a bank descriptor to a merchant and category.
Start free, no card required, most teams ship a first integration in under ten minutes.
Not another JSON page.
A production workflow in one call
One call in. A resolved merchant out.
Before Orsa
- A browser worker, proxy account, parser, retry queue, and schema contract for one endpoint.
- Product teams wait while platform teams debug website-specific failures.
- Every new data field becomes another brittle scraper branch.
After Orsa
- One call in. A resolved merchant out. With retries, rendering, and validation handled behind the API.
- The response shape is typed, documented, and ready for product code.
- Teams combine it with adjacent Orsa endpoints without adding vendors.
Teach the workflow,
then show the endpoint
Point Orsa at a merchant descriptor, let the platform handle the web work, and receive a response your product can trust.
Send a merchant descriptor
SQ *BLUE BOTTLE 4471
Render, retry, enrich
Orsa handles browser execution, proxy escalation, parsing, validation, caching, and typed response shaping behind the API.
One call in. A resolved merchant out.
Use the result in card feeds without owning the extraction stack.
- REST path
- /api/v1/brand/retrieveSame endpoint used by the SDK examples below.
- Input shape
- merchant descriptorSQ *BLUE BOTTLE 4471
- SDKs
- TypeScript, Python, cURLStart with TypeScript, Python, or direct cURL.
- Best first use
- Card feedsReplace cryptic strings with recognizable brands.
Performance your product
can actually plan around
Every endpoint page should answer the practical buying question: will this hold up once it leaves the demo?
More than the response.
The operating layer behind it
Stripe pages teach the system around the API: inputs, retries, observability, adjacent products, and the code path. This section does the same for Orsa endpoints.
- Typed response contracts for product code and AI tools.
- Browser, proxy, cache, and validation logic handled by Orsa.
- Direct fit for card feeds and expense automation.
Endpoint
/api/v1/brand/retrieve
Example input
SQ *BLUE BOTTLE 4471
Promise
One call in. A resolved merchant out.
Pairs with
NAICS Classification, Company Logos, Company Description
What teams ship with
the merchant, from the descriptor.
Each product page now speaks to the real workflow behind the endpoint, with concrete jobs instead of a generic feature list.
Card feeds
Replace cryptic strings with recognizable brands.
Expense automation
Route spend to the right GL without user edits.
Risk signals
Ground alerts in merchant identities, not raw strings.
Keep the code small.
Let Orsa do the messy part
Use the endpoint directly, then combine it with adjacent Orsa APIs as the workflow grows.
{
"transaction_info": "SQ *BLUE BOTTLE 4471",
"name": "Blue Bottle Coffee",
"domain": "bluebottlecoffee.com",
"naics": "722515",
"logo": "https://cdn.orsa.dev/bluebottlecoffee.com/logo.svg"
}Build the full workflow,
not another point solution
The best product integrations usually combine two or three Orsa endpoints behind one customer experience.
The questions teams ask
before shipping
Short answers for the practical details: rendering, limits, freshness, and how this fits into production.
Put this endpoint
in your product today
Try the live endpoint, then wire the same response into your app with one API key.
One API key for every Orsa endpoint · No card required to start.