Install Jentic One Beta

Connect the Swagger LINKA - OpenAPI 3.0.3 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Swagger LINKA - OpenAPI 3.0.3, 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%2Flimberfy.com%2Flimberfy" | 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%2Flimberfy.com%2Flimberfy" | 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 Swagger LINKA - OpenAPI 3.0.3 API.

Publish a purchase order with its supplier, client, totals, PDF, and NEC line details from an ERP

Update or remove a purchase order by its order number

Query purchase orders by number, currency, status, order type, or issue and reception date ranges

Look up supplier invoices by series number with filters for evaluation status, currency, and dates

GET STARTED

Start building with Swagger LINKA - OpenAPI 3.0.3 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Swagger LINKA - OpenAPI 3.0.3 API for, with concrete tasks.

★ Agent-driven purchase order sync through Jentic

An AI agent watching an ERP can push each approved purchase order to LINKA so suppliers see it in their portal, then confirm it landed by querying orders by number. Through Jentic the agent finds the publish and query operations by intent and loads their schemas, so the nested ordenCompra and detallesOrden payload is built from the schema instead of hand-written.

Search Jentic for 'publish a purchase order', send order OC-0001 with tipoOrden 'Suministro', moneda 'USD', and its detallesOrden lines, then query purchase orders with number=OC-0001 to confirm it was created.

Supplier invoice status checks

Accounts payable teams in Peru need to know whether each supplier invoice was accepted, observed, or rejected. The LINKA bill query filters by series number (sn), correlative number, evaluation status, currency, and issue or reception date range, so an agent can report on pending invoices without opening the portal.

Query bills with sn=F001 and eval_status=0 for issue dates from 01-06-2025 to 30-06-2025 and list the pending invoices.

Supplier onboarding

Before a supplier can work in LINKA, its company is registered by RUC with name, phone, and address, and each person who operates on its records gets a user with a DNI and role. The API covers registering, listing, updating, and removing both companies and users, and changing a user's password.

Register a supplier company with its name, ruc, phone, address, first_name, and last_name, then register a user for that ruc with username, password, dni, and role 4.

Key Endpoints

15 endpoints — the linka api from limberfy connects a buyer's erp to the linka supplier portal: it publishes purchase orders with their line items and pdf, updates or removes them by order number, and queries orders and supplier invoices by date range, currency, and evaluation status.

METHOD

PATH

DESCRIPTION

POST

/api/token/

Obtain an authentication token

POST

/api/purchase_order/

Create a purchase order

GET

/api/purchase_order/

Query purchase orders

PUT

/purchase_order/{numeroOrden}/

Update a purchase order

GET

/api/bill/

Query supplier invoices

POST

/v1/api/register_company/

POST

/v1/api/register_provider/

POST

/api/token/

Obtain an authentication token

POST

/api/purchase_order/

Create a purchase order

GET

/api/purchase_order/

Query purchase orders

PUT

/purchase_order/{numeroOrden}/

Update a purchase order

GET

/api/bill/

Query supplier invoices

POST

/v1/api/register_company/

POST

/v1/api/register_provider/

Why Jentic?

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

Setup

Wiring LINKA by hand means exchanging your RUC, username, and password for a JWT and building the nested ordenCompra and detallesOrden payload correctly. Through Jentic you install once, import LINKA from the API Directory, store the credential once, and your agent calls it.

Permission scoping

LINKA puts the order number and the supplier RUC in the URL path (/purchase_order/{numeroOrden}/ and /v1/api/get_providers/{RUC}/), so a rule can pin your agent to one purchase order or one supplier company. You choose the operations it may call, so destructive ones like deleting a supplier company or a purchase order are not included unless you add them.

Credential isolation

Your LINKA credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'publish a purchase order' or 'check invoice status', and Jentic returns the matching LINKA operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Swagger LINKA - OpenAPI 3.0.3 API through Jentic.

What authentication does the LINKA API use?

The LINKA API uses HTTP bearer authentication with a JWT per its OpenAPI spec. You obtain the token from the token operation by posting your ruc, username, and password, then send it in the Authorization header. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at request time.

Is there a Limberfy LINKA MCP server?

You don't need an MCP server to give your agent the LINKA API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the purchase order, bill, and supplier operations on demand without loading another server's tool definitions into its context.

Can I filter purchase orders by status with the LINKA API?

Yes. The purchase order query takes a status filter with values such as 0 for pending, 2 for completed, and 4 for partial, plus filters for order number, currency, total, order type (oc_type), and issue or reception date ranges.

What are the rate limits for the LINKA API?

The OpenAPI spec does not specify rate limits. Check with Limberfy at https://limberfy.com for current limits on your LINKA account.

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

Yes. For example, write a rule that allows only the purchase order query and the bill query, so the agent can report on orders and invoice status but cannot publish, change, or remove orders or touch supplier companies and users. Every call it makes is logged.

How do I check supplier invoice status with the LINKA API through Jentic?

Search Jentic for 'query supplier invoices', load the bill query operation, and pass the required series number sn with optional eval_status, currency, and date filters in DD-MM-YYYY format. Jentic injects your bearer token at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Limberfy Swagger LINKA - OpenAPI 3.0.3

AI ReadinessFoundational (D+)48/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceOrder Managementbearer15 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Publish, update, and look up purchase orders, query supplier invoices by series and status, and register supplier companies and their users on the LINKA portal.

Use for: I need to publish a purchase order from our ERP to the supplier portal, Find all purchase orders issued in USD last month, Check whether the invoices for series F001 were accepted, List all supplier users registered under this RUC

Not supported: Does not issue electronic invoices to SUNAT, pay suppliers, or track inventory. Use for publishing purchase orders, checking supplier invoice status, and onboarding suppliers on LINKA only.

The LINKA API from Limberfy connects a buyer's ERP to the LINKA supplier portal: it publishes purchase orders with their line items and PDF, updates or removes them by order number, and queries orders and supplier invoices by date range, currency, and evaluation status. It also registers supplier companies by their Peruvian RUC tax id and manages the supplier users who operate on each company's records. LINKA follows SUNAT rules for electronic payment vouchers in Peru.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

89%

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

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

42%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

52%

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

27%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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

75%

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: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Swagger LINKA - OpenAPI 3.0.3 to your agent

Capabilities

Start building with Swagger LINKA - OpenAPI 3.0.3 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Limberfy Swagger LINKA - OpenAPI 3.0.3

Jentic AI Readiness Score

Swagger LINKA - OpenAPI 3.0.3

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