SightMap® REST API

Name: SightMap® REST API
Brand: SightMap® REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey88 EndpointsREST

For Agents

Programmatically list accounts, view an account. Covers 88 operations with apiKey authentication.

Use for: I need to accounts, I want to view an account, Search for embeds, Find all view an embed

Install Jentic One Beta

Connect the SightMap® REST API to your agent

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

List accounts

View an account

Assign assets

Unassign assets

GET STARTED

Start building with SightMap® REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SightMap® REST API for, with concrete tasks.

★ CRM Operations

Use the SightMap® REST API to perform crm operations programmatically. The API provides 88 endpoints covering core functionality including list accounts, view an account, list embeds.

Call GET /accounts to list accounts

Automated assets/filters Management

Automate assets/filters operations by combining multiple SightMap® REST API endpoints. Agents can view an account and then list embeds in a single workflow.

Call GET /accounts/{account} to view an account, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SightMap® REST 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 'list accounts', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

88 endpoints — introduction the sightmap® api uses standard http verbs to communicate and http status codes to indicate status and errors.

METHOD

PATH

DESCRIPTION

GET

/accounts

List accounts

GET

/accounts/{account}

View an account

GET

/accounts/{account}/embeds

List embeds

GET

/accounts/{account}/embeds/{embed}

View an embed

GET

/accounts/{account}/assets

List assets

PUT

/accounts/{account}/assets

Assign assets

PUT

/accounts/{account}/assets/remove

Unassign assets

POST

/assets

Create an asset

GET

/accounts

List accounts

GET

/accounts/{account}

View an account

GET

/accounts/{account}/embeds

List embeds

GET

/accounts/{account}/embeds/{embed}

View an embed

GET

/accounts/{account}/assets

List assets

PUT

Why Jentic?

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

Credential isolation

SightMap® REST API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list accounts') and Jentic returns the matching SightMap® REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct SightMap® REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using SightMap® REST API through Jentic.

What authentication does the SightMap® REST API use?

The SightMap® REST API uses an API key passed in the `API-Key` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I list accounts with the SightMap® REST API?

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

What are the rate limits for the SightMap® REST 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 list accounts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list accounts'. Jentic returns the matching SightMap® REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the SightMap® REST API have?

The SightMap® REST API exposes 88 endpoints covering assets/filters, assets/units/descriptions, assets/pricing operations.

SightMap® REST API

Connect the SightMap® REST API to your agent

Capabilities

Start building with SightMap® REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs