Install Jentic One Beta

Connect the Segment API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Segment 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%2Fheysegment.com%2Fheysegment" | 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%2Fheysegment.com%2Fheysegment" | 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 API.

Deploy a site by starting a push, committing it, and watching the deploy status and logs

Create serverless functions for a site and publish, invoke, and version them

Collect form submissions on a site and route them to email or text recipients

Manage accounts, organizations, and businesses, and their provider and Google connections

Track a business's online reputation, including Google reviews, feedback, and review-request sequences

GET STARTED

Start building with Segment API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Segment API for, with concrete tasks.

★ Agent-Driven Site Deployment

An AI agent managing a client's website uses the Segment API through Jentic to deploy changes end to end: it starts a push, commits it, and polls the site's deploy status and logs until the deploy finishes. The same surface lets the agent create and invoke serverless functions and manage a site's assets and secrets. Every call is a bearer-authenticated request scoped to the credential's account.

Start a push for a site, commit it, then poll the deploy status until it reports success and read the logs

Form Submissions and Notifications

A site collects form submissions and routes them to the right people. The Segment API lists and reads submissions, toggles their email on or off, manages email recipients and templates, and can text a number about a submission's entries. This lets an application wire a contact form to email and SMS notifications without custom plumbing.

List a site's submissions, enable email on one, and add a recipient address to it

Reputation and Review Management

An agency tracks a client business's online reputation by reading its Google reviews, private feedback, and review-request messaging sequences. The Segment API exposes reputation metrics, review listings and replies, and the automation and destination behind review requests, scoped to a business by id. This gives a reporting agent a full read of how a business is performing on reviews.

For a business id, read the reputation metrics and list the latest Google reviews and private feedback

Key Endpoints

114 endpoints — the segment api from heysegment builds and deploys websites and runs the platform behind them: it starts and commits site pushes, reports deploy status and logs, creates and invokes serverless functions, and collects form submissions.

METHOD

PATH

DESCRIPTION

GET

/v1/account

Retrieve the credential's account

GET

/v1/account/sites

List sites

POST

/v1/sites/{siteId}/pushes

Start a deploy push for a site

POST

/v1/sites/{siteId}/pushes/{snapshotId}/commit

Commit a push

GET

/v1/sites/{siteId}/status

Get the site's deploy status

POST

/v1/sites/{siteId}/functions/{functionId}/invoke

Invoke a published function

POST

/v1/sites/{siteId}/submissions

Create a form submission

GET

/v1/businesses/{businessId}/reputation/reviews

List Google reviews and replies for a business

GET

/v1/account

Retrieve the credential's account

GET

/v1/account/sites

List sites

POST

/v1/sites/{siteId}/pushes

Start a deploy push for a site

POST

/v1/sites/{siteId}/pushes/{snapshotId}/commit

Commit a push

GET

/v1/sites/{siteId}/status

Get the site's deploy status

POST

/v1/sites/{siteId}/functions/{functionId}/invoke

Invoke a published function

POST

/v1/sites/{siteId}/submissions

Create a form submission

GET

/v1/businesses/{businessId}/reputation/reviews

List Google reviews and replies for a business

Why Jentic?

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

Setup

Wiring the Segment API by hand means handling its bearer credential, validating it with an explicit pre-authentication call, and threading account, business, and site ids through its many endpoints. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Segment puts the account, business, and site ids in the URL path (/v1/sites/{siteId}/..., /v1/businesses/{businessId}/...), so a rule can pin your agent to one site or one business and the operations you pick. You choose the operations it may call, so destructive ones like deleting a submission or a secret are not included unless you add them.

Credential isolation

Your Segment credential 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 'deploy a site' or 'list Google reviews', and Jentic returns the matching Segment operation with its input schema so the agent sends the right siteId or businessId without reading the reference docs.

FAQs

Specific to using Segment API through Jentic.

What authentication does the Segment API use?

Most resource operations authenticate with a bearer credential in the Authorization header, per its OpenAPI spec, where `/v1/account` is the credential's own account and an organization, business, or site beneath it is named by id in the path. A few endpoints, such as the ping and credential validation, need no credential. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time.

Can I deploy a site and run functions with the Segment API?

Yes. You start a push, commit it, and read the deploy status and logs, and you create, publish, and invoke serverless functions on a site. The same API also manages a site's assets, secrets, and form submissions, all scoped to the site by its siteId.

What are the rate limits for the Segment API?

The OpenAPI spec does not specify rate limits. For current limits, see the Heysegment documentation at https://www.heysegment.com.

How do I deploy a site through Jentic?

Search Jentic with a query like 'deploy a site', add the Segment API from the directory, and store your bearer credential once. Your agent starts a push for the site, commits it, and polls the deploy status until it succeeds. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Because the site and business ids live in the URL path, a Jentic rule can pin your agent to one site or one business, and you choose which operations it may call, such as reading reviews or deploy status while leaving delete operations out, with every call logged. That keeps an agent that only reports on reputation from ever touching a site deploy.

Is there a Segment API MCP server?

You don't need an MCP server to give your agent the Segment API. Jentic connects it directly from the API Directory: import it, store your bearer credential once, and your agent calls the site, submission, function, and reputation operations it needs on demand without loading another server's tool definitions into its context.

Heysegment Segment API

AI ReadinessFoundational (D-)42/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsCi Cdbearer114 EndpointsREST

For Agents

Deploy Heysegment sites with pushes and commits, run serverless functions, collect form submissions, and read a business's Google reviews, all over a bearer-authenticated REST API scoped by account, business, and site id.

Use for: Deploy a site by starting and committing a push, Check the deploy status and logs for a site, Invoke a published function on a site, List the form submissions on a site

Not supported: Does not host a customer data platform, run ad campaigns, or process payments. Use for managing Heysegment accounts, sites and deploys, form submissions, functions, and business reputation only.

The Segment API from Heysegment builds and deploys websites and runs the platform behind them: it starts and commits site pushes, reports deploy status and logs, creates and invokes serverless functions, and collects form submissions. Alongside the site surface it manages accounts, organizations, and businesses, and tracks each business's online reputation through Google reviews and review-request messaging. Every resource call authenticates with a bearer credential whose account, business, or site is named by id in the path.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

93%

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).

100%

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: FSignals: 4

19%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

81%

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: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Segment API to your agent

Capabilities

Start building with Segment API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Heysegment Segment API

Jentic AI Readiness Score

Segment 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