LIBERGENT FOR DEVELOPERS

Your app.
Marketplace search.
One API.

Bring product listings, original photos and source links into your storefront, comparison tool or app.

GET /api/v1/search?q=iphone%2015

{
  "apiVersion": "1",
  "mode": "live",
  "partial": false,
  "items": [
    { "title": "…", "url": "…" }
  ]
}

Illustrative response · real results include price, source, photos and freshness.

01Try it

Explore a simulated response without an account.

02Create a key

03Make a request

Call from your server. Put the results in your app.

Start with a demo

NO KEY NEEDED

See the response format before connecting your app. Demo and test keys use simulated data and never contact marketplaces.

Your API keys

Use one account for your applications. Each key has its own name and permissions; usage limits are shared across your account.

Checking API key availability…

Copy. Paste. Search.

Save your key as LIBERGENT_API_KEY in your server environment. Use a test key first, then switch to a live key for real results.

Search query

Server-side example

curl --fail-with-body "https://libergent.com/api/v1/search?q=iphone%2015&limit=10" \
  -H "Authorization: Bearer $LIBERGENT_API_KEY"

Never put the API key in frontend JavaScript, a public repository, or a NEXT_PUBLIC_ variable. Cache results on your server before showing them to visitors.

Connect an AI agent

Use the REST API as a tool in your own agent, or connect an MCP client to /api/v1/mcp. Both use the same test/live API keys, search permissions, cache and account quotas.

Discoverable tools

search_products finds products; list_sources lists your allowed marketplaces. Set details=true when your key permits listing enrichment.

Connect from your agent host

Choose the MCP example above. Supply your key in the Authorization header from a server secret. This read-only connection does not contact sellers or make purchases.

MCP requires separate deployment enablement. Automatic sign-in through hosted assistant platforms requires OAuth account linking, which is not included yet.

A small, predictable API

OpenAPI specification

Search

GET /api/v1/search

q is required. Optional: sites (comma-separated), limit (1–20), and details=true with listing details permission.

Specialized filters are optional: category=full_fur_coat and material=natural|synthetic|unknown. Leave them out for general product search.

Sources

GET /api/v1/sources

Initial API coverage: OLX, Publi24 and Okazii. The default is OLX. Coverage and availability vary by source; empty results are possible.

Search is a bounded sample of up to 20 candidates, not a complete marketplace inventory.

Starter limits

Live: 200 requests/day, 10/minute.
Test: 1,000 requests/day, 60/minute.

Cached requests count too. HTTP 429 includes Retry-After. There is no billing or automatic paid upgrade in this release.

Freshness & failures

Results are cached for 15 minutes. Inspect partial, sources and lastVerifiedAt. Missing values are null; availability can be unknown.

401: replace an invalid key. 403: check permissions. 502/503: retry later. Live requests can take about 30 seconds; use a 35-second client timeout.

Your app.Marketplace search.One API.