Enable Networks Address API

Name: Address API
Brand: Address API
Availability: InStock

Browse all Swaggerhub Enable Networks APIs

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontapiKey2 Endpoints

Install Jentic One Beta

Connect the Address API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Address 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 Address API.

GET_proactive

PUT_proactive

Integrate Address API into automated workflows

Query and filter Address API records by parameters

GET STARTED

Start building with Address API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically get_proactive, put_proactive. Covers 2 operations with apiKey authentication.

Use for: I need to get_proactive, I want to put_proactive, Get the current status of Address API resources, List all records from Address API

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

Use Cases

Patterns agents use Address API for, with concrete tasks.

★ E-Commerce Operations

Use the Address API to perform e commerce operations programmatically. The API provides 2 endpoints covering core functionality including get_proactive, put_proactive.

Call GET /proactive/{fsl_id} to get_proactive

Data Retrieval and Monitoring

Query Address 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.

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

AI Agent Integration via Jentic

AI agents discover and call Address 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.

Search Jentic for 'get_proactive', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — update proactive value based on the current proactive value calculated from the combination of work order type and primary incident type.

METHOD

PATH

DESCRIPTION

GET

/proactive/{fsl_id}

GET_proactive

PUT

/proactive/{fsl_id}

PUT_proactive

GET

/proactive/{fsl_id}

GET_proactive

PUT

/proactive/{fsl_id}

PUT_proactive

Why Jentic?

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

Credential isolation

Your Address 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.

Intent-based discovery

Agents search Jentic by intent such as 'get the proactive record for a service location', and Jentic returns the matching Address API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Address API through Jentic.

What authentication does the Address API use?

The Address 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.

Can I get_proactive with the Address API?

Yes. Use the GET /proactive/{fsl_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Address 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 get_proactive through Jentic?

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

How many endpoints does the Address API have?

The Address API exposes 2 endpoints covering proactive operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Address API operations and credentials the agent may use. Because the service location id sits in the URL path (/proactive/{fsl_id}), you can pin the agent to a single location and grant only GET /proactive/{fsl_id} so it reads that proactive record but cannot change it, adding PUT /proactive/{fsl_id} only when you want it to update. The stored API key is injected at execution time under those rules, so the agent can only call the operations you approve.