Install Jentic One Beta

Connect the CloudYA API to your agent

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

Create and update sales invoices and convert quotes into invoices

Maintain customers, suppliers, and sales leads for a company

Keep accounting accounts, cost centers, and bank accounts

Apply Dominican tax rules with ITBIS, ISR and ITBIS retentions, and NCF fiscal sequences

GET STARTED

Start building with CloudYA API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CloudYA API for, with concrete tasks.

★ Agent-Driven Invoicing Through Jentic

An AI agent handling billing can create and send invoices in CloudYA through Jentic instead of integrating the API by hand. The agent adds the customer if needed, creates the invoice with its line items, applies the correct Dominican tax, and registers a payment when it clears. Each resource has its own path, so the agent's reach is easy to bound to invoicing operations.

Create a customer, issue a sales invoice with two line items and ITBIS applied, and register a payment against it

Automated Invoicing and Payment Recording

CloudYA turns quotes into invoices, sends them by email, and records payments against them so a billing workflow runs end to end. A service can convert an accepted quote to a sale, generate the invoice PDF, email it to the customer, and apply the payment once received.

Convert an accepted quote into an invoice, email it to the customer, and apply the received payment to it

Dominican Electronic Invoicing and Tax Compliance

For businesses in the Dominican Republic, CloudYA models the fiscal detail an invoice needs: ITBIS, ISR and ITBIS retentions, and NCF sequences, plus a connection to an electronic fiscal provider and certificate validation. That lets an invoice carry the correct tax treatment and fiscal numbering for DGII reporting.

Connect a company to its electronic fiscal provider, validate the certificate, and issue an invoice with the correct NCF and ITBIS

Expense Receipt Capture With OCR and Approval

CloudYA captures expense receipts as drafts, attaches a photo or PDF, runs OCR to read the amounts, and moves each receipt through submit, review, approve, or reject steps. A finance team can digitize paper receipts and register the resulting expense once it is approved.

Create an expense receipt draft, attach a PDF, run OCR on it, submit it for review, and approve it to register the expense

Key Endpoints

246 endpoints — the cloudya api runs accounting and invoicing for a company, with a focus on dominican republic fiscal rules.

METHOD

PATH

DESCRIPTION

GET

/api/v2/sales/

List invoices

POST

/api/v2/sales/

Create an invoice

GET

/api/v2/customers/

List customers

POST

/api/v2/customers/

Create a customer

POST

/api/v2/cotizaciones/{id}/convert_to_sale/

Convert a quote into an invoice

POST

/api/v2/salePayments/

Create and apply an invoice payment

GET

/api/v2/accountingAccount/

List accounting accounts

GET

/api/v2/items/

List items

GET

/api/v2/sales/

List invoices

POST

/api/v2/sales/

Create an invoice

GET

/api/v2/customers/

List customers

POST

/api/v2/customers/

Create a customer

POST

/api/v2/cotizaciones/{id}/convert_to_sale/

Convert a quote into an invoice

POST

/api/v2/salePayments/

Create and apply an invoice payment

GET

/api/v2/accountingAccount/

List accounting accounts

GET

/api/v2/items/

List items

Why Jentic?

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

Setup

Wiring the CloudYA API by hand means obtaining a token from its token endpoints, passing it in the Authorization header, and keeping track of the v1, v2, and v3 resource paths that make up its surface. Through Jentic you install once, import CloudYA from the API Directory, store the token once, and your agent calls it.

Permission scoping

CloudYA groups each resource under its own path, such as the sales and customers paths, so a rule can bound your agent to the operations it needs, like reading and creating invoices. You choose the operations it may call, so destructive ones like deleting a customer or voiding an invoice are not included unless you add them.

Credential isolation

Your CloudYA 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 an invoice or register a payment, and Jentic returns the matching CloudYA operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using CloudYA API through Jentic.

What authentication does the CloudYA API use?

The CloudYA API authenticates with a token in the Authorization header, per its OpenAPI spec; you obtain and refresh that token through its token endpoints. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.

Can I create invoices with the CloudYA API?

Yes. You can create and update sales invoices, convert a quote into an invoice, duplicate or void one, send it by email, and register payments against it. Reports and a PDF rendering of an invoice are available too.

Does the CloudYA API support Dominican electronic invoicing and taxes?

Yes. The API models Dominican fiscal concepts including ITBIS, ISR and ITBIS retentions, and NCF fiscal sequences, and it connects a company to an electronic fiscal provider and validates its electronic certificate. That lets invoices carry the correct tax treatment for the Dominican Republic.

How do I create an invoice with the CloudYA API through Jentic?

Install Jentic One, then import CloudYA from the API Directory and store your token once. Your agent searches by intent such as create an invoice, and Jentic returns the create-invoice operation with its input schema so the agent supplies the customer and line items and gets the invoice back. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a CloudYA API MCP server?

You don't need an MCP server to give your agent the CloudYA API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the invoice, customer, and accounting operations on demand. Operations are discovered when the agent needs them, so they do not fill its context ahead of time.

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

Yes. Because each resource sits under its own path, you can write a rule that allows only the operations your agent needs, such as reading and creating invoices, and leaves customer deletion or invoice voiding out of reach. Every call the agent makes is logged.

Cloudya Do CloudYA API

AI ReadinessNon-Ready (F)39/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceAccountingapiKey246 EndpointsREST

For Agents

Create and manage sales invoices and quotes, record payments, maintain customers and accounting accounts, and apply Dominican ITBIS, ISR, and NCF tax rules. Capture expense receipts with OCR and sync invoices with WooCommerce.

Use for: I want to create a sales invoice for a customer, Find all invoices from the last month, Convert a quote into an invoice, Register a payment against an invoice

Not supported: Does not handle payroll, point-of-sale hardware, or bank transfers. Use for accounting, invoicing, and Dominican tax management for a company only.

The CloudYA API runs accounting and invoicing for a company, with a focus on Dominican Republic fiscal rules. It creates and manages sales invoices and quotes, records payments, maintains customers, suppliers, and sales leads, and keeps a chart of accounting accounts, cost centers, and bank accounts. Dominican tax handling covers ITBIS, ISR and ITBIS retentions, and NCF fiscal sequences, with a connection to an electronic fiscal provider. It also captures expense receipts with OCR and approval flows, and syncs items and invoices with WooCommerce.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

64%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

27%

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

28%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

51%

OperationId Quality

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

16%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

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

32%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CloudYA API to your agent

Capabilities

Start building with CloudYA API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cloudya Do CloudYA API

Jentic AI Readiness Score

CloudYA 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