Install Jentic One Beta

Connect the WholeStory Zapier API to your agent

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

Create a session token

Validate a session token

Integrate WholeStory Zapier API into automated workflows

Query and filter WholeStory Zapier API records by parameters

Monitor WholeStory Zapier API operational status and events

GET STARTED

Start building with WholeStory Zapier API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use WholeStory Zapier API for, with concrete tasks.

★ Identity and Authentication Operations

Use the WholeStory Zapier API to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including create a session token, validate a session token, create a candidate invitation.

Call POST /sessions to create a session token

Automated Sessions Management

Automate sessions operations by combining multiple WholeStory Zapier API endpoints. Agents can validate a session token and then create a candidate invitation in a single workflow.

Call GET /sessions to validate a session token, then verify the result

AI Agent Integration via Jentic

AI agents discover and call WholeStory Zapier 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 none tokens manually.

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

Key Endpoints

3 endpoints — wholestory is a technology platform for employers that integrates the candidate's pivotal life experiences into the screening and interview process.

METHOD

PATH

DESCRIPTION

POST

/sessions

Create a session token

GET

/sessions

Validate a session token

POST

/invitations

Create a candidate invitation

POST

/sessions

Create a session token

GET

/sessions

Validate a session token

POST

/invitations

Create a candidate invitation

Why Jentic?

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

Setup

Wiring the WholeStory Zapier API by hand still means writing the HTTP client, response parsing, and retry handling for its sessions and invitations endpoints yourself. Through Jentic you install once, import the WholeStory Zapier API from the API Directory, and your agent calls it.

Permission scoping

The WholeStory Zapier API carries its targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as listing sessions or creating an invitation. You choose that allowed set, and only the operations you name are available to the agent.

Credential isolation

Any WholeStory 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 'list sessions' or 'create an invitation', and Jentic returns the matching WholeStory Zapier API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using WholeStory Zapier API through Jentic.

What authentication does the WholeStory Zapier API use?

The WholeStory Zapier API uses no authentication. 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 a session token with the WholeStory Zapier 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 WholeStory Zapier 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 a session token through Jentic?

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

How many endpoints does the WholeStory Zapier API have?

The WholeStory Zapier API exposes 3 endpoints covering sessions, invitations operations.

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

Yes. Because you run Jentic One yourself, you decide which WholeStory Zapier API operations your agent may call, and only the ones you name are available to it. This API carries its targets in the request body rather than the URL path, so you can allow just what a task needs, such as validating a session token while blocking candidate invitation creation. Your own rules govern both the permitted operations and the credentials the agent may use.

Tellyourwholestory WholeStory Zapier API

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationnone3 EndpointsREST

For Agents

Programmatically create a session token, validate a session token. Covers 3 operations.

Use for: I need to a session token, I want to validate a session token, Search for a candidate invitation, List all records from WholeStory Zapier API

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

WholeStory is a technology platform for employers that integrates the candidate's pivotal life experiences into the screening and interview process. This API provides Zapier integration endpoints for session management and candidate invitations. The API exposes 3 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

48%

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.

60%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the WholeStory Zapier API to your agent

Capabilities

Start building with WholeStory Zapier API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tellyourwholestory WholeStory Zapier API

Jentic AI Readiness Score

WholeStory Zapier 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