canonical: https://jentic.com/apis/swaggerhub.enable-networks/address-lookup-api

# Enable Networks Address Lookup Api

The Address Lookup API is used to find unique Enable address identifiers (FSL Fibre Service Location) and associated information. The API has two endpoints which are: - addresses - which is used to return a list of addresses - addresses/id - which is used to get detailed information about the address. Before you can access the production Apis, you need to complete the production onboarding process. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically access Address Lookup API resources. Covers 3 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Access Address Lookup API resources via REST API
- Manage e commerce data programmatically
- Integrate Address Lookup API into automated workflows
- Query and filter Address Lookup API records by parameters
- Monitor Address Lookup API operational status and events

## Use cases

### E-Commerce Operations

The API provides 3 endpoints for e commerce operations.

Example prompt: Execute a primary operation against the Address Lookup API

### Data Retrieval and Monitoring

Query Address Lookup API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Address Lookup API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Address Lookup API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'address lookup API', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **Addresses** — Operations for addresses
- **Version** — Operations for version

## Why Jentic

- **Setup:** Wiring the Address Lookup API by hand means supplying its Okta-verified bearer token in the Authorization header, targeting the correct Enable Networks host, and handling responses yourself. Through Jentic you install once, import the Address Lookup API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Address Lookup API puts the address id in the URL path (/addresses/{id}), so a rule can pin your agent to reading a specific address alongside the address search: you choose the operations it may call, so only the lookups you allow are available.
- **Credential handling:** Your Address Lookup API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search for an address' or 'get address details by id', and Jentic returns the matching Address Lookup API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Address Lookup API use?

The Address Lookup API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### What are the rate limits for the Address Lookup API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I use address lookup API through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use address lookup API'. Jentic returns the matching Address Lookup API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Address Lookup API have?

The Address Lookup API exposes 3 endpoints covering addresses, version operations.

### Does the Address Lookup API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

### Can I limit what my agent is allowed to do with the Address Lookup API?

Yes. Jentic One is self-hosted, so you set the rules that decide which Address Lookup API operations your agent may call and which credentials it may use. You can allow only the address search while blocking the lookup-by-id endpoint, or the reverse, and because the address id sits in the URL path (/addresses/{id}) you can pin the agent to reading a specific address. The agent can call only the operations you have explicitly permitted.