Install Jentic One Beta

Connect the ManageTradeX - Document API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ManageTradeX - Document 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%2Fmanagetradex.my%2Fmanagetradex-document" | 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%2Fmanagetradex.my%2Fmanagetradex-document" | 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 ManageTradeX - Document API.

Submit an invoice, credit note, debit note, refund note, or self-billed document with POST /documents/{docType} for MyInvois validation

Retrieve a submitted document's details by transactionId, adding artefacts such as the PDF with includeArtefacts

Cancel a validated document with PUT /documents/{docType}/cancel by passing its docNo and a reason

Validate a supplier or buyer TIN with GET /validateTin/{tin} using an idType of BRN, NRIC, ARMY, or PASSPORT and its idValue

GET STARTED

Start building with ManageTradeX - Document API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ManageTradeX - Document API for, with concrete tasks.

★ Agent-run e-invoice submission through Jentic

An accounting agent validates the buyer's TIN, submits the invoice for MyInvois validation, and later fetches the document details with its PDF once the callback reports success. Through Jentic the agent finds each operation by intent, the OAuth2 client credentials stay in the developer's own Jentic One instance, and a rule can let the agent submit and read documents while cancellation stays out.

Call GET /validateTin/{tin} with idType 'BRN' and the buyer's registration number as idValue, then POST /documents/IN with the invoice payload

Credit notes and cancellations

When an invoice is wrong, the document type in the path selects the correction: CN for a credit note, DN for a debit note, or RN for a refund note, each submitted through POST /documents/{docType}. A validated document can instead be cancelled outright with PUT /documents/{docType}/cancel, which requires the docNo and a reason as query parameters.

Call PUT /documents/IN/cancel with docNo 'INV-1001' and reason 'Incorrect amount'

Buyer and supplier identity checks

Before issuing an e-invoice, the counterparty's Tax Identification Number can be confirmed with GET /validateTin/{tin}, which needs both an idType such as BRN, NRIC, ARMY, or PASSPORT and the matching idValue. GET /lookup/participants/{peppolId} shows whether a buyer can receive documents over Peppol and which document types it supports.

Call GET /validateTin/C1234567890 with idType 'BRN' and idValue '201901234567', then GET /lookup/participants/{peppolId} for the buyer

Key Endpoints

5 endpoints — the managetradex document api submits e-invoicing documents to the managetradex platform for validation and processing against malaysia's myinvois system.

METHOD

PATH

DESCRIPTION

POST

/documents/{docType}

Submit a document

GET

/documents/{docType}

Get document details

PUT

/documents/{docType}/cancel

Cancel a document

GET

/validateTin/{tin}

Validate a TIN

GET

/lookup/participants/{peppolId}

Look up a Peppol participant

POST

/documents/{docType}

Submit a document

GET

/documents/{docType}

Get document details

PUT

/documents/{docType}/cancel

Cancel a document

GET

/validateTin/{tin}

Validate a TIN

GET

/lookup/participants/{peppolId}

Look up a Peppol participant

Why Jentic?

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

Setup

Wiring the ManageTradeX Document API by hand means running the OAuth 2.0 client credentials exchange, building MyInvois-shaped invoice payloads, and handling the validation callback yourself. Through Jentic you install once, import the API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

ManageTradeX puts the document type in the URL path, so a rule can pin your agent to one docType such as credit notes and the operations you pick. You choose the operations it may call, so the cancel operation is not included unless you add it.

Credential isolation

Your ManageTradeX client 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 'submit an e-invoice' or 'validate a TIN', and Jentic returns the matching ManageTradeX operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ManageTradeX - Document API through Jentic.

Is there a ManageTradeX MCP server?

You don't need an MCP server to give your agent the ManageTradeX Document API. Jentic connects it directly from the API Directory: import it, store your OAuth2 client credentials once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

What authentication does the ManageTradeX Document API use?

Per its OpenAPI spec, the ManageTradeX Document API uses OAuth 2.0 with the client credentials grant, requesting tokens from the /oauth2/token path. Through Jentic the client credentials are stored encrypted by your own Jentic One instance and the token exchange happens at execution time, so the credentials never enter the agent's context.

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

Yes. For example, write a rule that allows POST /documents/CN and GET /documents/CN, so the agent can submit and check credit notes only, while invoices and the cancel operation stay out of reach. Every call it makes is logged on your own machine.

Which document types can I submit?

The docType path value covers IN for invoices, CN for credit notes, DN for debit notes, and RN for refund notes, plus the self-billed SIN, SCN, SDN, and SRN variants. Documents are submitted in JSON or XML and the validation result is delivered to your callback.

How do I submit an e-invoice through Jentic?

Install Jentic One, import the ManageTradeX Document API from the directory, and search for 'submit a Malaysian e-invoice'. Jentic returns the submit document operation with its input schema; your agent sets docType to IN and sends the invoice with fields such as senderId, docNo, docDate, currency, supplier, and buyer. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the ManageTradeX Document API?

The OpenAPI spec does not specify rate limits. Check the ManageTradeX documentation at https://managetradex.my for current limits. Note that the spec's server is the sandbox host api-sbox.managetradex.my.

Managetradex My ManageTradeX - Document API

Browse all Managetradex My APIs

AI ReadinessFoundational (C+)58/100

See full scorecard

Community OpenAPI document · agent-readyFinanceTaxoauth25 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Submit Malaysian e-invoices and credit or debit notes for MyInvois validation, fetch or cancel submitted documents, validate a TIN, and look up a Peppol participant.

Use for: Submit this invoice to MyInvois through ManageTradeX, Check whether a buyer's TIN is valid for their business registration number, Get the validation result and PDF for a submitted invoice, Cancel invoice INV-1001 because the amount was wrong

Not supported: Does not handle tax calculation, payment collection, bookkeeping, or sending invoices over the Peppol network. Use for submitting, retrieving, and cancelling MyInvois e-invoicing documents and validating TINs only.

The ManageTradeX Document API submits e-invoicing documents to the ManageTradeX platform for validation and processing against Malaysia's MyInvois system. It accepts invoices, credit notes, debit notes, refund notes, and their self-billed variants in JSON or XML, reports the validation result through a callback, and returns document details by transactionId with optional artefacts such as the PDF. It also cancels a validated document by docNo with a reason, validates a supplier or buyer Tax Identification Number against an identity type such as BRN or NRIC, and looks up a Peppol participant and the document types it supports.

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

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

23%

Example Density

How richly the API is illustrated with examples.

69%

Example Validity

Percentage of examples that conform to their schemas.

75%

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

67%

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.

56%

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ManageTradeX - Document API to your agent

Capabilities

Start building with ManageTradeX - Document API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Managetradex My ManageTradeX - Document API

Jentic AI Readiness Score

ManageTradeX - Document 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