Install Jentic One Beta

Connect the Planful REST API to your agent

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

Import financial data

Export financial data

List scenarios

Use Cases

Patterns agents use Planful REST API for, with concrete tasks.

★ Finance and Accounting Operations

Use the Planful REST API to perform finance operations programmatically. The API provides 4 endpoints covering core functionality including import financial data, export financial data, list scenarios.

Call POST /data/import to import financial data

GET STARTED

Start building with Planful REST API

Explore with Jentic One

View OpenAPI Document

Automated Data Management

Automate data operations by combining multiple Planful REST API endpoints. Agents can export financial data and then list scenarios in a single workflow.

Call POST /data/export to export financial data, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'import financial data', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — planful financial planning and analysis api for managing budgets, forecasts, consolidations, and financial data.

METHOD

PATH

DESCRIPTION

POST

/data/import

Import financial data

POST

/data/export

Export financial data

GET

/scenarios

List scenarios

GET

/dimensions

List dimensions

POST

/data/import

Import financial data

POST

/data/export

Export financial data

GET

/scenarios

List scenarios

GET

/dimensions

List dimensions

Why Jentic?

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

Setup

Wiring the Planful REST API by hand means setting up its OAuth token auth and hand-building the request plumbing for its data import, export, scenario and dimension calls yourself. Through Jentic you install once, import Planful from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Planful's operations take their target in the request body rather than the URL path, so scoping is operations-only: limit the agent to the operations it needs, such as reading scenarios or dimensions. You choose which operations it may call, so ones like importing or exporting data are not included unless you add them.

Credential isolation

Your Planful OAuth 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 'import financial data' or 'list scenarios', and Jentic returns the matching Planful operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Planful REST API through Jentic.

What authentication does the Planful REST API use?

The Planful REST API uses OAuth 2.0 for authorization. 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 import financial data with the Planful REST API?

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

What are the rate limits for the Planful REST 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 import financial data through Jentic?

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

How many endpoints does the Planful REST API have?

The Planful REST API exposes 4 endpoints covering data, metadata, planning operations.

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

Yes. Because you run Jentic One yourself, you decide which Planful operations your agent may call, and your own rules govern the OAuth credential it uses. Planful takes its target in the request body rather than the URL path, so scoping is at the operation level: you can allow read-only calls such as GET /scenarios and GET /dimensions while withholding writes like POST /data/import and POST /data/export. Any operation you do not grant stays unavailable to the agent.

Planful REST API

Name: Planful REST API
Brand: Planful REST API
Availability: InStock

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingoauth24 EndpointsREST

For Agents

Programmatically import financial data, export financial data. Covers 4 operations with oauth2 authentication.

Use for: I need to import financial data, I want to export financial data, Search for scenarios, Find all dimensions

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

Planful financial planning and analysis API for managing budgets, forecasts, consolidations, and financial data. The API exposes 4 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

35%

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

37%

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.

50%

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: ASignals: 1

85%

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

Capabilities

Use Cases

Start building with Planful REST API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Planful REST API

Jentic AI Readiness Score

Planful REST 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