Install Jentic One Beta

Connect the Frappe Framework REST API to your agent

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

List, filter, and paginate any DocType via GET /api/resource/{doctype}

Create new records of any DocType with POST /api/resource/{doctype}

Read, update, and delete a specific record by name via /api/resource/{doctype}/{name}

Invoke any whitelisted server-side method via /api/method/{dotted_path}

GET STARTED

Start building with Frappe Framework REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Frappe Framework REST API for, with concrete tasks.

★ ERPNext Automation

An operations team automates routine ERPNext tasks like creating Sales Invoices from external orders, updating stock entries, and running monthly close reports. Because every ERPNext document is a Frappe DocType, the same /api/resource pattern handles all of them with a consistent JSON schema and filter syntax.

POST /api/resource/Sales Invoice with customer, items, and posting_date, then update its status with PUT /api/resource/Sales Invoice/{name}

Custom Business App Backend

A team building a custom ERPNext app exposes server-side Python methods for complex workflows that a single CRUD call cannot express. The /api/method endpoint lets the frontend or an external integration trigger that method by its dotted Python path, with the Frappe permission system enforced on every call.

POST /api/method/{dotted_path} with the JSON arguments expected by the Python method, then read the resulting message from the response

Data Sync to External Systems

An integration script keeps ERPNext customers and items in sync with an external CRM or e-commerce store. The script paginates GET /api/resource/{doctype} with a modified filter, fetches changed records since the last run, and pushes them downstream. The same pattern works in reverse for inbound sync.

GET /api/resource/Customer?filters=[["modified",">","2026-06-01"]]&limit_page_length=100 and post each result to the downstream CRM

AI Agent ERP Operator

An agent receives natural-language requests like 'create a quote for Acme for 10 widgets at 50 each' and translates them into Frappe API calls through Jentic. The agent never sees the api_key or api_secret - Jentic injects them at execution time - and gets a structured response it can read back to the user.

Search Jentic for 'create a Sales Invoice in ERPNext', load the resource schema, and execute POST /api/resource/Sales Invoice with the parsed line items

Key Endpoints

10 endpoints — frappe is the open-source python framework that powers erpnext, and every site automatically exposes its doctypes through a rest api.

METHOD

PATH

DESCRIPTION

GET

/api/resource/{doctype}

List records of a DocType with filters and pagination

POST

/api/resource/{doctype}

Create a new record of a DocType

GET

/api/resource/{doctype}/{name}

Read a single record by name

POST

/api/method/{dotted_path}

Invoke a whitelisted server-side method

POST

/api/method/upload_file

Upload a file and attach it to a DocType

POST

/api/method/login

Authenticate by username and password

GET

/api/method/frappe.auth.get_logged_user

Identify the currently authenticated user

GET

/api/resource/{doctype}

List records of a DocType with filters and pagination

POST

/api/resource/{doctype}

Create a new record of a DocType

GET

/api/resource/{doctype}/{name}

Read a single record by name

POST

/api/method/{dotted_path}

Invoke a whitelisted server-side method

POST

/api/method/upload_file

Upload a file and attach it to a DocType

POST

/api/method/login

Authenticate by username and password

GET

/api/method/frappe.auth.get_logged_user

Identify the currently authenticated user

Why Jentic?

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

Setup

Wiring the Frappe Framework REST API by hand means choosing between its api_key/api_secret token header and OAuth2 bearer auth, resolving your own site host into the {site} base URL, and building your own retry and error handling. Through Jentic you install once, import Frappe from the API Directory, store the chosen credential once, and your agent calls it.

Permission scoping

Frappe puts the DocType and record name in the URL path (/api/resource/{doctype}/{name}), so a rule can pin your agent to one DocType: it can read and create records of that type. You choose the operations it may call, so arbitrary server-method invocation via /api/method is not included unless you add it.

Credential isolation

Your Frappe api_key/api_secret pair or OAuth2 bearer token 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 'create a Sales Invoice' or 'find all Customers', and Jentic returns the matching /api/resource or /api/method operation with its input schema so the agent does not need to know the dotted path or DocType name in advance.

FAQs

Specific to using Frappe Framework REST API through Jentic.

What authentication does the Frappe REST API use?

Frappe supports two schemes: a token header in the form 'Authorization: token api_key:api_secret', and OAuth2 bearer tokens for apps that go through the Frappe OAuth flow. Through Jentic, both kinds of credential are stored encrypted in the vault and the agent only sees a scoped execution token.

Can I create any DocType record with the Frappe REST API?

Yes. POST to /api/resource/{doctype} with a JSON body containing the field values. The same endpoint pattern works for Sales Invoice, Customer, Item, Employee, or any custom DocType - Frappe enforces the DocType's own validation and permission rules on the call.

What are the rate limits for the Frappe REST API?

Frappe does not impose framework-level rate limits in the spec. ERPNext Cloud applies per-site fair-use limits and a Frappe site administrator can configure rate limiting through the System Settings DocType for self-hosted installations.

How do I call a custom server method through Jentic?

Search Jentic for 'call a Frappe server method', load the /api/method/{dotted_path} schema, and execute it with the dotted Python path of the whitelisted method (for example erpnext.stock.get_item_details.get_item_details) plus the JSON arguments. The response carries whatever the Python function returned.

Is the Frappe REST API free?

Frappe and ERPNext are open source under the GNU GPLv3, so self-hosted installations have no licensing cost for API access. ERPNext Cloud is a paid hosted plan and the same REST API is included with every paid tier.

How do I upload a file and attach it to a DocType?

POST to /api/method/upload_file as multipart/form-data with the file payload plus the doctype and docname fields that name the parent record. Frappe stores the file and creates the attachment link automatically.

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

Yes. Because Frappe puts the DocType and record name directly in the URL path (/api/resource/{doctype}/{name}), a rule in your self-hosted Jentic One can pin the agent to a single DocType and let it only read and create records of that type. You decide which operations the agent may call, so arbitrary server-method invocation through /api/method is excluded unless you explicitly add it. Your api_key/api_secret pair or OAuth2 bearer token stays with your own instance and is injected at execution time, never entering the agent's prompt or context.

Frappe Framework REST API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsProject ManagementapiKey, bearer10 EndpointsREST

For Agents

Read, create, update, and delete any DocType on a Frappe or ERPNext site, plus invoke server-side methods and upload files. Authentication is token (api_key:api_secret) or OAuth2 bearer.

Use for: I need to create a new Sales Invoice in ERPNext, List all Customers with outstanding balances over 1000, Update the status of a Purchase Order to Closed, Upload a receipt PDF and attach it to an Expense Claim

Not supported: Does not handle real-time messaging, payment processing, or external email delivery - use for CRUD on Frappe DocTypes and server-method invocation only.

Frappe is the open-source Python framework that powers ERPNext, and every site automatically exposes its DocTypes through a REST API. The 10 endpoints in this spec cover authentication, generic CRUD on any DocType via /api/resource, dotted-path remote method calls via /api/method, file uploads, and the current logged-in user lookup. Because every business object - Sales Invoice, Purchase Order, Customer, Item, Employee - is a DocType, the same handful of endpoints reach hundreds of resources without a per-resource wrapper.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

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

21%

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

50%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

90%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

62%

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

55%

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

Capabilities

Start building with Frappe Framework REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Frappe Framework REST API

Jentic AI Readiness Score

Frappe Framework 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