Turn a request into search constraints
A hosted helper: natural language in, the exact constraint object POST /v1/agent/search accepts out,
plus unresolved — the parts of the request it could not map to a constraint.
It runs a model and debits the store’s Agent Compute credits at the true cost of the call; usage
reports what was debited. A failed call keeps no credits. It is limited to 60 calls a minute per client
and 1,000 an hour per key, in addition to the standard limits.
Authorizations
API Key Authentication
Use your API key in the Authorization header:
Key Types:
Secret Keys (Server-Side Only):
- Format:
tybrite_sk_live_*(production) ortybrite_sk_test_*(sandbox) - Full read/write access to all endpoints
- ⚠️ NEVER expose in client-side code or public repositories
- Required for: write operations, authentication, payment verification, AI recommendations
Publishable Keys (Client-Safe):
- Format:
tybrite_pk_live_*(production) ortybrite_pk_test_*(sandbox) - Read-only access (GET requests only, plus POST semantic search)
- ✅ Safe for client-side JavaScript, mobile apps, and public code
- Allowed for: browsing products, search, CMS content, pricing queries
Endpoint-Specific Requirements:
- Authentication endpoints (
/v1/auth/*): Secret key required - Payment verification (
POST /v1/payments/verify): Secret key required - AI Recommendations (
POST /v1/recommendations): Secret key required - Semantic Search (
POST /v1/search): Both key types allowed (read-only operation) - All write operations: Secret key required
- All read operations: Both key types allowed
Using a publishable key for restricted operations returns 403 Forbidden.
Body
500Response
The constraints
Where each figure in data was read from.
production, sandbox ISO 4217 code every amount in data is expressed in.
What the call cost. Present on the hosted-helper tools only.

