Install Jentic One Beta

Connect the Smore API to your agent

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

Get user profile

List forms

Create a webhook

Delete a webhook

Monitor Smore API operational status and events

Use Cases

GET STARTED

Start building with Smore API

Explore with Jentic One

View OpenAPI Document

Automated Profile Management

Automate profile operations by combining multiple Smore API endpoints. Agents can list forms and then create a webhook in a single workflow.

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

AI Agent Integration via Jentic

AI agents discover and call Smore 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, oauth2 tokens manually.

Search Jentic for 'get user profile', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — the smore api allows you to manage forms, retrieve user profile information, and configure webhooks for form submissions.

METHOD

PATH

DESCRIPTION

GET

/me

Get user profile

GET

/forms

List forms

POST

/webhooks

Create a webhook

DELETE

/webhooks/{webhookId}

Delete a webhook

GET

/me

Get user profile

GET

/forms

List forms

POST

/webhooks

Create a webhook

DELETE

/webhooks/{webhookId}

Delete a webhook

Why Jentic?

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

Setup

Wiring Smore by hand means running its OAuth2 authorization-code flow or bearer auth against smore.im and managing retries yourself. Through Jentic you install once, import the Smore API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Smore reads run on account-level resources like /me and /forms, so scope the agent to the operations it needs, such as reading the profile and listing forms. You choose which operations are allowed, so creating or deleting a webhook is not included unless you add it.

Credential isolation

Your Smore 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 'get my user profile' or 'list my forms', and Jentic returns the matching Smore operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Smore API through Jentic.

What authentication does the Smore API use?

The Smore API uses bearer, oauth2 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 get user profile with the Smore API?

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

What are the rate limits for the Smore 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 get user profile through Jentic?

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

How many endpoints does the Smore API have?

The Smore API exposes 4 endpoints covering profile, forms, webhooks operations.

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

Yes. Jentic One is self-hosted, so you run it and your own rules decide which Smore operations and credentials the agent may use. You can scope the agent to read-only calls like GET /me for the user profile and GET /forms to list forms, while withholding the webhook operations. Creating a webhook with POST /webhooks or deleting one with DELETE /webhooks/{webhookId} stays off limits unless you explicitly allow it.

Smore API

AI ReadinessAI-Ready (A-)75/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationbearer, oauth24 EndpointsREST

For Agents

Programmatically get user profile, list forms. Covers 4 operations with bearer, oauth2 authentication.

Use for: I need to user profile, I want to forms, Search for a webhook, Find all a webhook

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

The Smore API allows you to manage forms, retrieve user profile information, and configure webhooks for form submissions. Authentication is performed via OAuth 2.0 Bearer tokens. The API exposes 4 endpoints secured with bearer, oauth2 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

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

93%

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

67%

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.

69%

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

75%

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 Smore API to your agent

Capabilities

Use Cases

Start building with Smore API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Smore API

Jentic AI Readiness Score

Smore 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