Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cobra · API de facturación electrónica SRI, 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%2Ffacturacobra.com%2Ffacturacobra" | shStep 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%2Ffacturacobra.com%2Ffacturacobra" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Cobra · API de facturación electrónica SRI API.
Issue an SRI-authorized electronic document (invoice, credit note, debit note, or withholding) via POST /documents
Check a document's SRI authorization status via GET /documents/{id}/status
Void an authorized document under the SRI rules via POST /documents/{id}/anular
Resolve a RUC or cedula against the SRI registry via GET /sri-lookup/{identificacion}
GET STARTED
Maintain reusable contacts and products via POST /contacts and POST /products
Register webhooks for authorization events via POST /webhooks and remove them when no longer needed
Patterns agents use Cobra · API de facturación electrónica SRI API for, with concrete tasks.
★ AI agent invoicing assistant
An AI billing assistant issues Ecuadorian electronic invoices on behalf of a business and reports back when the SRI authorizes them. Through Jentic it looks up the customer's RUC, emits the comprobante, and polls the authorization status, all without a person opening the Cobra dashboard. Jentic injects the API key at call time, so the agent never holds the secret.
Search Jentic for 'issue an SRI-authorized invoice', validate the buyer with GET /sri-lookup/{identificacion}, issue the document with POST /documents, then poll GET /documents/{id}/status until it is authorized
Issue and confirm a comprobante
Businesses must get each sale authorized by the SRI before it is valid, and they need to know the moment that happens. Cobra signs and transmits the comprobante on POST /documents and exposes its authorization state on a status endpoint, so a workflow can emit the document and confirm authorization rather than assume it. Webhooks can push the same authorization event instead of polling.
Call POST /documents to emit the invoice, then read GET /documents/{id}/status to confirm the SRI authorized it before sending the customer their copy
Returns and voids
When a sale is reversed, the business issues a credit note or voids the original document under the SRI's rules. Cobra creates the credit note through the same document endpoint and voids an authorized comprobante through a dedicated void action, keeping the fiscal trail correct. This lets an agent handle a return without hand-editing fiscal records.
Issue a credit note with POST /documents, or void the original authorized document with POST /documents/{id}/anular when the sale is fully reversed
Customer tax-ID validation
Before invoicing, a business confirms the buyer's tax identity so the comprobante is issued against a valid RUC or cedula. Cobra's SRI lookup resolves the identifier against the official registry, so an onboarding or checkout flow can validate the buyer up front and avoid rejected documents. The reusable contacts endpoint then stores the validated party for future invoices.
Call GET /sri-lookup/{identificacion} with the buyer's RUC, and on a valid result store the party with POST /contacts for reuse on future documents
14 endpoints — the cobra api issues electronic tax documents authorized by ecuador's sri, including invoices, credit notes, debit notes, and withholding receipts, from a single rest surface.
METHOD
PATH
DESCRIPTION
/documents
Issue a comprobante (invoice, credit note, debit note, or withholding)
/documents/{id}/status
Get a document's SRI authorization status
/documents/{id}/anular
Void an authorized comprobante
/sri-lookup/{identificacion}
Look up a RUC or cedula in the SRI registry
/contacts
Create or update a contact
/products
Create a product
/webhooks
Register a webhook for authorization events
/documents
List comprobantes
/documents
Issue a comprobante (invoice, credit note, debit note, or withholding)
/documents/{id}/status
Get a document's SRI authorization status
/documents/{id}/anular
Void an authorized comprobante
/sri-lookup/{identificacion}
Look up a RUC or cedula in the SRI registry
/contacts
Create or update a contact
/products
Create a product
/webhooks
Register a webhook for authorization events
/documents
List comprobantes
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Cobra API by hand means managing its X-API-Key header, keeping sandbox and production keys apart, and building the issue-then-poll-authorization loop against the SRI yourself. Through Jentic you install once, import Cobra from the API Directory, store the key once, and your agent calls it.
Permission scoping
Cobra puts each document id in the URL path, such as /documents/{id}, so a rule can let your agent read and check documents while keeping fiscal writes out. You choose the operations it may call, so issuing a comprobante with POST /documents or voiding one with POST /documents/{id}/anular is not included unless you add it.
Credential isolation
Your Cobra API 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 'issue an SRI-authorized invoice' or 'look up a RUC', and Jentic returns the matching Cobra operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Cobra · API de facturación electrónica SRI API through Jentic.
What authentication does the Cobra API use?
The Cobra API authenticates with an API key sent in the X-API-Key header, in the format mfact_<prefix>_<secret>, per its OpenAPI spec, and a sandbox key runs against the test environment while a production key issues real documents. When you call it through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt, logs, or context.
Can I issue an SRI-authorized invoice with the Cobra API?
Yes. Call POST /documents with the document type and line items to emit an invoice, credit note, debit note, or withholding, and Cobra signs it and transmits it to the SRI. Confirm the outcome with GET /documents/{id}/status, which reports the SRI authorization state for that document.
Can I void or credit an already-issued document with the Cobra API?
Yes. Issue a credit note through POST /documents, or void an authorized document with POST /documents/{id}/anular, which applies the SRI's void rules. That keeps the fiscal record correct when a sale is reversed without hand-editing authorized documents.
What are the rate limits for the Cobra API?
The OpenAPI spec does not specify rate limits for the Cobra API. Check the Cobra documentation for current limits, design your agent to back off when the API signals that it is being throttled, and prefer webhooks over polling for authorization events.
How do I issue an invoice through Jentic?
Search Jentic for 'issue an SRI-authorized invoice' to load the Cobra document operation with its input schema, validate the buyer with GET /sri-lookup/{identificacion}, then call POST /documents and read GET /documents/{id}/status to confirm authorization. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Cobra API?
Yes. Because you run Jentic One yourself, you decide which Cobra operations the agent may call. You can allow read operations such as GET /documents and GET /documents/{id}/status so the agent can list and check comprobantes, while leaving out issuing or voiding documents unless you add them, and every call the agent makes is logged.
For Agents
Issue SRI-authorized electronic documents for Ecuador through Cobra: emit invoices, credit notes, debit notes, and withholdings, check their authorization status, void them, and look up a RUC or cedula in the SRI registry.
Use for: Issue an electronic invoice authorized by the SRI, Check whether a comprobante was authorized by the SRI, Void an authorized invoice under the SRI rules, Look up a customer's RUC in the SRI registry
Not supported: Does not handle payment collection, bank reconciliation, or payroll. Use for issuing and managing SRI-authorized electronic tax documents in Ecuador only.
The Cobra API issues electronic tax documents authorized by Ecuador's SRI, including invoices, credit notes, debit notes, and withholding receipts, from a single REST surface. It signs each comprobante and transmits it to the SRI, exposes the authorization status, and can void an authorized document under the SRI rules. Contacts and products are maintained for reuse on documents, an SRI lookup resolves a RUC or cedula against the tax registry, and webhooks deliver authorization events. Authentication uses an API key sent in the X-API-Key header, with separate sandbox and production keys.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>