Locu App Locu Public API

Name: Locu Public API
Brand: Locu Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey4 EndpointsREST

For Agents

Look up local businesses and venue records by id, list locations, or search by attributes such as name, city, or category.

Install Jentic One Beta

Connect the Locu Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Locu Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Locu Public API.

List location records with pagination across the Locu venue database

Retrieve a single location by its id with full metadata

Create a new location entity through POST /locations

Search the venue database by attributes via GET /search

GET STARTED

Start building with Locu Public API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Locu Public API, keeping it validated and agent-ready. Locu provides programmatic access to a curated database of local business and location records, covering names, addresses, categories, and venue metadata. The API exposes list, retrieve, and search operations for location entities, allowing developers to look up venues by id or filter by attributes such as city or category. Typical uses include populating store finders, enriching CRM records, and powering local-discovery features.

Use Cases

Patterns agents use Locu Public API for, with concrete tasks.

★ Local Business Search Feature

Power a search bar that returns nearby restaurants, bars, or shops by querying GET /search with attribute filters. Locu returns ranked venue records with addresses and categories so the front-end can render results without additional lookups.

Call GET /search with q='coffee' and city='Seattle' and return the top 10 venue ids and names.

CRM Location Enrichment

Append canonical address and category metadata to CRM contact records by looking up each contact's listed business through GET /locations/{id} or /search. This standardises field-rep data and prevents duplicate entries caused by spelling variations.

For each CRM contact's company name, call GET /search with the name and persist the matched location id and address.

Store Finder Backend

Drive a store-finder page by listing locations with GET /locations and filtering by city. Pagination is supported so large catalogues stream cleanly to the client. Each record includes the metadata needed for a map pin without joining external data.

Call GET /locations with city='Austin' and limit=50, then map each result onto the store-finder map.

AI Agent Venue Lookup via Jentic

Agents that answer 'where can I get X near here' can call Locu through Jentic without managing the API key. Jentic exposes the search and retrieve operations as MCP tools so the agent picks the right one by intent.

Through Jentic, search 'find local businesses', load the Locu /search schema, and execute it with the user's query and city.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for locu public api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/locations

List location records

POST

/locations

Create a new location

GET

/locations/{id}

Retrieve a single location by id

GET

/search

Search the venue database

GET

/locations

List location records

POST

/locations

Create a new location

GET

/locations/{id}

Retrieve a single location by id

GET

/search

Search the venue database

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Locu API key is stored encrypted in the Jentic vault and injected at execution time so the raw secret never reaches the agent's context window or logs.

Intent-based discovery

Agents search by intent (e.g. 'find a local business') and Jentic returns the matching Locu operation with its input schema, so the agent invokes the right endpoint without reading docs.

Time to first call

Direct Locu integration: a few hours for auth and pagination handling. Through Jentic: under 10 minutes — search, load, execute.

FAQs

Specific to using Locu Public API through Jentic.

Why is there no official OpenAPI spec for Locu Public API?

Locu does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Locu Public API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Locu Public API use?

The API uses an API key sent in the request header (ApiKeyAuth scheme). Through Jentic the key is stored in the encrypted vault and injected at execution, never exposed to the agent's prompt or logs.

Can I search for venues by city with the Locu Public API?

Yes. Use GET /search with a query string and supported filter parameters. The response returns a list of matching venue records with id, name, and address fields you can use directly.

What are the rate limits for the Locu Public API?

The spec does not declare numeric rate limits. Treat the API as throttled and back off on HTTP 429 responses. Jentic's executor surfaces 429s to the agent so it can retry with delay.

How do I look up a venue by id through Jentic?

Run `pip install jentic`, search for 'look up a local business', load the Locu GET /locations/{id} operation, and execute it with the venue id. Jentic handles auth and returns the parsed JSON record.

Is the Locu Public API free?

Locu's public API access tiers are not declared in the spec. Check locu.app for current pricing and quota allocations before high-volume use.

Locu App Locu Public API

Connect the Locu Public API to your agent

Capabilities

Start building with Locu Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs