Install Jentic One Beta

Connect the Way We Do Integration API to your agent

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

Delete all webhook registrations

Get a webhook registration

Add a new user

Find user

GET STARTED

Start building with Way We Do Integration API

Explore with Jentic One

View OpenAPI Document

Automated Checklist Instance Activity Management

Automate checklist instance activity operations by combining multiple Way We Do Integration API endpoints. Agents can delete all webhook registrations and then get a webhook registration in a single workflow.

Call DELETE /v1/webhook to delete all webhook registrations, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Way We Do Integration 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 'register for a webhook event', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

19 endpoints — restful api endpoints for integrating external applications with way we do.

METHOD

PATH

DESCRIPTION

POST

/v1/webhook

DELETE

/v1/webhook

Delete all webhook registrations

GET

/v1/webhook/{webhookId}

Get a webhook registration

DELETE

/v1/webhook/{webhookId}

Delete a webhook registration

POST

/v1/Users

Add a new user

GET

/v1/Users

Find user

GET

/v1/Users/{userId}

Get a user

GET

/v1/TimeZones

List time zones

POST

/v1/webhook

DELETE

/v1/webhook

Delete all webhook registrations

GET

/v1/webhook/{webhookId}

Get a webhook registration

DELETE

/v1/webhook/{webhookId}

Delete a webhook registration

POST

/v1/Users

Add a new user

GET

/v1/Users

Find user

GET

/v1/Users/{userId}

Get a user

GET

/v1/TimeZones

List time zones

Why Jentic?

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

Setup

Wiring the Way We Do Integration API by hand means learning its API key header, pointing at api.waywedo.com, and handling responses yourself. Through Jentic you install once, import the Way We Do Integration API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Way We Do puts the resource id in the URL path (/v1/webhook/{webhookId}, /v1/Users/{userId}), so a rule can pin your agent to one webhook or user and nothing else. You choose the operations it may call, so destructive ones like deleting a webhook are not included unless you add them.

Credential isolation

Your Way We Do API 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 'register for a webhook event' or 'list users', and Jentic returns the matching Way We Do operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Way We Do Integration API through Jentic.

What authentication does the Way We Do Integration API use?

The Way We Do Integration API uses an API key passed 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 register for a webhook event with the Way We Do Integration API?

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

What are the rate limits for the Way We Do Integration 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 register for a webhook event through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'register for a webhook event'. Jentic returns the matching Way We Do Integration API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Way We Do Integration API have?

The Way We Do Integration API exposes 19 endpoints covering checklist instance activity, checklist instance collaborators, checklist instance comments operations.

Can I limit what my agent is allowed to do with the Way We Do Integration API?

Yes. Because you run Jentic One yourself, your own rules decide which Way We Do operations and credentials the agent may use. Since Way We Do puts the resource id in the URL path, such as /v1/webhook/{webhookId} and /v1/Users/{userId}, a rule can pin the agent to a single webhook or user and nothing else. You also choose the operations it may call, so destructive ones like deleting a webhook are excluded unless you add them.

Way We Do Integration API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey19 EndpointsREST

For Agents

Programmatically register for a webhook event, delete all webhook registrations. Covers 19 operations with apiKey authentication.

Use for: I need to register for a webhook event, I want to all webhook registrations, Search for a webhook registration, Find all a webhook registration

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

RESTful API endpoints for integrating external applications with Way We Do. The API exposes 19 endpoints secured with apiKey authentication.

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

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

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

29%

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.

54%

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 Way We Do Integration API to your agent

Capabilities

Start building with Way We Do Integration API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Way We Do Integration API

Jentic AI Readiness Score

Way We Do Integration 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