Install Jentic One Beta

Connect the Segment Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Segment 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsegmentapis.com%2Fsegmentapis" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsegmentapis.com%2Fsegmentapis" | 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 Segment Public API.

Create Source

List Sources

Get Source

Update Source

Delete Source

GET STARTED

Start building with Segment Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Marketing Operations

Use the Segment Public API to perform marketing operations programmatically. The API provides 30 endpoints covering core functionality including create source, list sources, get source.

Call POST /sources to create source

Automated Sources Management

Automate sources operations by combining multiple Segment Public API endpoints. Agents can list sources and then get source in a single workflow.

Call GET /sources to list sources, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Segment Public 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 bearer tokens manually.

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

Key Endpoints

30 endpoints — the segment public api allows you to manage segment workspaces and their resources including sources, destinations, warehouses, spaces, and more.

METHOD

PATH

DESCRIPTION

POST

/sources

Create Source

GET

/sources

List Sources

GET

/sources/{sourceId}

Get Source

PATCH

/sources/{sourceId}

Update Source

DELETE

/sources/{sourceId}

Delete Source

POST

/sources/{sourceId}/labels

Add Labels to Source

PUT

/sources/{sourceId}/labels

Replace Labels in Source

POST

/sources/{sourceId}/write-keys

Create Write Key for Source

POST

/sources

Create Source

GET

/sources

List Sources

GET

/sources/{sourceId}

Get Source

PATCH

/sources/{sourceId}

Update Source

DELETE

/sources/{sourceId}

Delete Source

POST

/sources/{sourceId}/labels

Add Labels to Source

PUT

/sources/{sourceId}/labels

Replace Labels in Source

POST

/sources/{sourceId}/write-keys

Create Write Key for Source

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Segment Public API by hand means obtaining its bearer token, threading it onto every call, and building each source, label, and write-key request yourself. Through Jentic you install once, import Segment Public from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Segment Public API puts the source id in the URL path (/sources/{sourceId}/...), so a rule can pin your agent to one source: it can manage that source's labels and write keys and nothing else. You choose the operations it may call, so destructive ones like deleting a source are not included unless you add them.

Credential isolation

Your Segment Public API token 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 'create a source' or 'add a source write key', and Jentic returns the matching Segment Public API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Segment Public API through Jentic.

What authentication does the Segment Public API use?

The Segment Public API uses a Bearer token 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 create source with the Segment Public API?

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

What are the rate limits for the Segment Public 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 create source through Jentic?

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

How many endpoints does the Segment Public API have?

The Segment Public API exposes 30 endpoints covering sources, destinations, warehouses operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Segment Public API operations and credentials the agent may use. Since the source id sits in the URL path (/sources/{sourceId}/labels, /sources/{sourceId}/write-keys), you can pin the agent to a single source so it manages only that source's labels and write keys. You also choose which operations it may call, so a destructive one like DELETE /sources/{sourceId} is excluded unless you add it.

Segment Public API

Name: Segment Public API
Brand: Segment Public API
Availability: InStock

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingSeo Sembearer30 EndpointsREST

For Agents

Programmatically create source, list sources. Covers 30 operations with bearer authentication.

Use for: I need to source, I want to sources, Search for source, Find all source

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

The Segment Public API allows you to manage Segment Workspaces and their resources including Sources, Destinations, Warehouses, Spaces, and more. The API exposes 30 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

46%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

62%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Segment Public API to your agent

Capabilities

Start building with Segment Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Segment Public API

Jentic AI Readiness Score

Segment Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness