Install Jentic One Beta

Connect the Formo Public API to your agent

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

Ingest product events for a project and attach them to wallet profiles

Read KPIs such as sessions, pageviews, bounce rate, and session duration

Build conversion funnels and retention cohorts over tracked events

Report revenue and transaction volume as time-series or grouped by a metric

Run a SQL query directly against the analytics data

GET STARTED

Start building with Formo Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Formo Public API for, with concrete tasks.

★ Agent-Driven Product Analytics

An AI agent connected through Jentic answers a product question by reading KPIs, building a funnel, and checking retention, so a founder gets an activation read without opening a dashboard. Because Formo exposes a direct SQL query operation, the agent can drop to a custom query when the prebuilt reports do not cover the question.

Report the last 30 days of KPIs, build a signup-to-purchase funnel, and return the week-four retention for new wallets

Event Ingestion Pipeline

A web3 application streams product events into Formo using the project write key, so every wallet action lands in one place for analysis. The analytics endpoints then read those events as KPIs, flows, and revenue, so the same ingested data powers both dashboards and ad-hoc queries.

Ingest this batch of wallet events, then confirm they appear in the event time-series

Revenue and Lifecycle Reporting

A reporting workflow reads revenue overviews and lifecycle stages, groups revenue by a chosen metric, and watches alerts for sudden changes, so a team tracks monetisation and churn without manual spreadsheets. Lifecycle stages such as New, Returning, Power user, At Risk, and Churned let the workflow segment wallets by where they are in their journey.

Pull the revenue overview for this quarter and list how many wallets are in each lifecycle stage

Key Endpoints

55 endpoints — the formo public api ingests product events and reports on how wallets use a web3 application, so a team can measure activation, retention, and revenue without building its own analytics stack.

METHOD

PATH

DESCRIPTION

POST

/v0/raw_events

Ingest product events

GET

/v0/kpis

Get KPIs such as sessions and pageviews

GET

/v0/funnel

Get a multi-step conversion funnel

GET

/v0/retention

Get user retention cohorts

POST

/v0/query

Execute a SQL query

GET

/v0/profiles

Search wallet profiles

GET

/v0/boards/{boardId}/charts/{chartId}/query

Execute a saved chart query

POST

/v0/raw_events

Ingest product events

GET

/v0/kpis

Get KPIs such as sessions and pageviews

GET

/v0/funnel

Get a multi-step conversion funnel

GET

/v0/retention

Get user retention cohorts

POST

/v0/query

Execute a SQL query

GET

/v0/profiles

Search wallet profiles

GET

/v0/boards/{boardId}/charts/{chartId}/query

Execute a saved chart query

Why Jentic?

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

Setup

Wiring the Formo API by hand means juggling a workspace API key for analytics and a separate write key for event ingestion, splitting calls between the api and events hosts, and handling the 402 payment flow on metered endpoints. Through Jentic you install once, import Formo from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which operations your agent may call, so you can allow reading KPIs and running queries while leaving destructive ones like deleting an alert or a segment out. Rules bound which operations run, so the agent reports on the data you grant and nothing else.

Credential isolation

Your Formo 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 'build a conversion funnel' or 'ingest product events', and Jentic returns the matching Formo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Formo Public API through Jentic.

Is there a Formo MCP server?

You don't need an MCP server to give your agent the Formo API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can ingest events and read KPIs, funnels, and retention straight away, with no extra server to run and no tool definitions sitting in the agent's context.

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

Yes. Write a rule that allows only the operations the agent needs, such as reading KPIs and running queries, and leave alert deletion and segment changes out. Every call the agent makes is logged, so you can see exactly which reports it ran.

What authentication does the Formo API use?

The Formo API authenticates with a workspace API key presented as a bearer token on api.formo.so per its OpenAPI spec. Event ingestion uses a separate project SDK write key, also a bearer token, and metered endpoints answer a 402 challenge with a payment payload in the X-PAYMENT or Authorization header. Through Jentic the key is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

Can I run a custom query with the Formo API?

Yes. Beyond the prebuilt KPI, funnel, and retention reports, one operation runs a SQL query directly against the analytics data, and saved charts on a board expose their own query endpoint. An agent can read a prebuilt metric or drop to SQL when a question needs it.

What are the rate limits for the Formo API?

The OpenAPI spec does not state request rate limits for the Formo API. For current limits and fair-use guidance, check the provider documentation at https://api.formo.so.

How do I report product metrics through Jentic?

Import the Formo Public API from the Jentic API Directory, then have your agent issue a request such as 'show me the conversion funnel for signups'. Jentic matches the intent to the funnel operation and returns its input schema so the agent builds the correct request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Formo So Formo Public API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsProduct AnalyticsapiKey, bearer55 EndpointsREST

For Agents

Ingest product events and read KPIs, funnels, retention, revenue, and wallet profiles in Formo, or run a SQL query against the data. Authenticates with a workspace API key as a bearer token, with a separate write key for event ingestion.

Use for: Ingest a batch of product events for a project, Get the KPIs for the last thirty days, Build a conversion funnel across three events, Retrieve retention cohorts for new wallets

Not supported: Does not send marketing campaigns, process payments, or host a data warehouse. Use for product-event ingestion and analytics reporting only.

The Formo Public API ingests product events and reports on how wallets use a web3 application, so a team can measure activation, retention, and revenue without building its own analytics stack. You send raw events, then read KPIs, funnels, retention cohorts, lifecycle stages, and user-flow transitions, or run a SQL query directly against the data. Wallet profiles, segments, alerts, and dashboards of saved charts let you organise the analysis, and smart-contract records tie on-chain activity to the metrics.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D-Signals: 4

70%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

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

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

51%

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.

77%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C+Signals: 1

59%

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

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Formo Public API to your agent

Capabilities

Start building with Formo Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Formo So Formo Public API

Jentic AI Readiness Score

Formo Public 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