Install Jentic One Beta

Connect the Second Street API to your agent

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

Create API session

Get consumer subscriptions

Update consumer subscriptions

List promotions

Monitor Second Street API operational status and events

GET STARTED

Start building with Second Street API

Explore with Jentic One

View OpenAPI Document

Automated Analytics Management

Automate analytics operations by combining multiple Second Street API endpoints. Agents can get consumer subscriptions and then update consumer subscriptions in a single workflow.

Call GET /consumers/{consumerId}/subscriptions to get consumer subscriptions, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Second Street 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 'create API session', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

11 endpoints — second street provides audience engagement, contest, and promotion management.

METHOD

PATH

DESCRIPTION

POST

/sessions

Create API session

GET

/consumers/{consumerId}/subscriptions

Get consumer subscriptions

PUT

/consumers/{consumerId}/subscriptions

Update consumer subscriptions

GET

/consumers/{consumerId}/profile

Get consumer profile

POST

/promotions

Create promotion

GET

/promotions

List promotions

GET

/promotions/{promotionId}

Get promotion

GET

/promotions/{promotionId}/analytics

Get promotion analytics

POST

/sessions

Create API session

GET

/consumers/{consumerId}/subscriptions

Get consumer subscriptions

PUT

/consumers/{consumerId}/subscriptions

Update consumer subscriptions

GET

/consumers/{consumerId}/profile

Get consumer profile

POST

/promotions

Create promotion

GET

/promotions

List promotions

GET

/promotions/{promotionId}

Get promotion

GET

/promotions/{promotionId}/analytics

Get promotion analytics

Why Jentic?

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

Setup

Wiring the Second Street API by hand means creating a session, carrying its X-Session-Token header on every call, and building consumer and promotion requests yourself. Through Jentic you install once, import Second Street from the API Directory, store the key once, and your agent calls it.

Permission scoping

Second Street puts the consumer and promotion ids in the URL path (/consumers/{consumerId}/... and /promotions/{promotionId}/...), so a rule can pin your agent to one promotion: it can read that promotion and its analytics and nothing else. You choose the operations it may call, so writes like updating a consumer's subscriptions are not included unless you add them.

Credential isolation

Your Second Street 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 'read a promotion's analytics' or 'get a consumer profile', and Jentic returns the matching Second Street operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Second Street API through Jentic.

What authentication does the Second Street API use?

The Second Street API uses an API key passed in the `X-Session-Token` 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 API session with the Second Street API?

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

What are the rate limits for the Second Street 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 API session through Jentic?

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

How many endpoints does the Second Street API have?

The Second Street API exposes 11 endpoints covering analytics, authentication, consumers operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Second Street operations and credentials your agent may use. Because Second Street puts consumer and promotion ids in the URL path, a rule can pin the agent to a single promotion so it reads only that promotion and its analytics and nothing else. You pick the operations it can call, so write actions like updating a consumer's subscriptions stay off limits unless you add them.

Second Street API

Name: Second Street API
Brand: Second Street API
Availability: InStock

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingSeo SemapiKey11 EndpointsREST

For Agents

Programmatically create API session, get consumer subscriptions. Covers 11 operations with apiKey authentication.

Use for: I need to API session, I want to consumer subscriptions, Search for consumer subscriptions, Find all consumer profile

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

Second Street provides audience engagement, contest, and promotion management. The API provides endpoints for managing consumer subscriptions, profiles, ballot data, ads, campaigns, messaging, analytics, and promotions. The API exposes 11 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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

50%

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

51%

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.

55%

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: C-Signals: 1

50%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Second Street API to your agent

Capabilities

Start building with Second Street API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Second Street API

Jentic AI Readiness Score

Second Street 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