Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Saldor 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%2Fsaldor.com%2Fsaldor" | 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%2Fsaldor.com%2Fsaldor" | 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 Saldor API.
Create a purchase, publish it for approval, and send its purchase order to the vendor
Receive items against a purchase and record item receipts, including parsing an uploaded packing slip
Upload a bill PDF, match it to a purchase, set per-line GL coding, and send it to Brex Bill Pay
Review three-way match edges between purchases, receipts, and invoices, then accept or reject pairings
GET STARTED
Invite vendors to onboard, approve them, and store their payment, tax, and compliance details
Run a sourcing event: build the RFX questionnaire, send it to candidates, compare quotes, and award
Approve, reject, or send back workflow steps and report spend against budgets for a period
Patterns agents use Saldor API for, with concrete tasks.
★ AI agent procurement assistant
An AI agent embedded in a team's chat turns a request like 'order 10 monitors from Dell' into a tracked purchase. Through Jentic the agent searches for 'create a purchase', loads the Saldor operation with its input schema, and posts the vendor, lines, amount, and currency while the bearer token is injected at call time. It can then publish the draft so Saldor's approval workflow takes over.
POST /api/purchases with vendor_name, currency USD, and two lines, then POST /api/purchases/{id}/publish to submit it for approval
Accounts payable three-way match
AP teams must confirm that what was ordered, received, and invoiced line up before paying. Saldor derives match edges between purchases, item receipts, and bills, exposes derived invoice and receipt states, and lets a reviewer accept or reject pairings. Exceptions that block payment can be assigned to a person or team queue.
List GET /api/matches for one purchase_id, check GET /api/bills/{id}/state for the linked bill, and accept the pairing if it matches
Bill intake and coding
Vendor invoices arrive as PDFs and need coding before payment. POST /api/bills/upload takes the file, the bill can be matched to a purchase by purchase_id, and the coding operations return an auto-suggestion that can be applied per line. A coded bill can then be sent to Brex Bill Pay through the connected integration.
Upload a bill PDF with POST /api/bills/upload, match it to a purchase with POST /api/bills/{id}/purchase, apply the coding suggestion, and send it to Brex
Vendor onboarding
New suppliers must supply payment, tax, and compliance details before they can be paid. Saldor creates an onboarding request from a contact_name and contact_email, sends the invite, lets the buyer message the vendor or request changes, and approves or rejects the submission. Approved vendors carry addresses, allow-listed email domains, and team access.
Create a vendor onboarding request for a contact email, then approve it once the vendor's tax details are present
Competitive sourcing
For larger buys, procurement runs an RFX before choosing a supplier. Saldor sourcing events hold questionnaire sections and questions, candidate vendors, and RFX documents, and once published they collect quotes into a comparison grid. The buyer awards the event and the purchase accepts the sourcing award.
Create a sourcing event, add two candidate vendors, publish the RFX, and fetch the quote comparison grid
276 endpoints — the saldor api runs a procure-to-pay workflow: purchase requests and orders, item receipts, vendor bills, and three-way matching between them.
METHOD
PATH
DESCRIPTION
/api/purchases
Create a purchase
/api/purchases/{id}/order/send
Send the purchase order to the vendor
/api/purchases/{id}/receive
Receive items on a purchase
/api/bills/upload
Upload a bill PDF
/api/bills/{id}/purchase
Match a bill to a purchase
/api/matches
List derived match edges
/api/vendor-onboarding-requests
Create and invite a vendor
/api/workflow-nodes/{id}/approve
Approve a workflow step
/api/purchases
Create a purchase
/api/purchases/{id}/order/send
Send the purchase order to the vendor
/api/purchases/{id}/receive
Receive items on a purchase
/api/bills/upload
Upload a bill PDF
/api/bills/{id}/purchase
Match a bill to a purchase
/api/matches
List derived match edges
/api/vendor-onboarding-requests
Create and invite a vendor
/api/workflow-nodes/{id}/approve
Approve a workflow step
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Saldor by hand means creating a key in console Settings, sending it as a bearer token, unwrapping the data envelope on every response, and chaining purchase, receipt, bill, and match calls in the right order. Through Jentic you install once, import Saldor from the API Directory, store the key once, and your agent calls it.
Permission scoping
Saldor puts the purchase, bill, and vendor id in the URL path (/api/purchases/{id}, /api/bills/{id}), so a rule can pin your agent to one purchase or one bill and the operations you pick. You choose the operations it may call, so sensitive ones like setting vendor payment details, deleting a vendor, or undoing events are not included unless you add them.
Credential isolation
Your Saldor 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 'create a purchase order' or 'match a bill to a PO', and Jentic returns the matching Saldor operation with its input schema, so the agent picks the right call from a large surface without reading the reference.
Alternatives and complements available in the Jentic catalogue.
Specific to using Saldor API through Jentic.
What authentication does the Saldor API use?
Per its OpenAPI spec, the Saldor API uses a bearer token on every operation: create an API key in Settings at console.saldor.com and send it as `Authorization: Bearer <key>`. Through Jentic the key is held by your own instance and added at call time, so it stays out of the agent's context.
Can I match a vendor bill to a purchase order with the Saldor API?
Yes. POST /api/bills/{id}/purchase links a bill to a purchase with the required purchase_id. GET /api/matches lists derived match edges filterable by purchase_id, receipt_id, or invoice_id, and POST /api/matches/accept or /api/matches/reject confirms or rejects a pairing.
What are the rate limits for the Saldor API?
The OpenAPI spec does not specify rate limits. Check the Saldor documentation at https://docs.saldor.com for current limits before running bulk bill uploads or vendor imports.
Is there a Saldor MCP server?
You don't need an MCP server to give your agent Saldor. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent finds the purchase, bill, and approval operations it needs by intent instead of loading the whole surface into its context.
How do I send a purchase order to a vendor through Jentic?
Search Jentic for 'send a purchase order to the vendor', load POST /api/purchases/{id}/order/send, and execute it with the purchase id. You can preview the vendor email first with GET /api/purchases/{id}/order/email-preview. 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 Saldor API?
Yes. For an AP assistant, write a rule that allows the bill upload, coding, and match-review operations, and the agent can process invoices while purchase approvals, vendor payment details, and team membership stay off its list. Every call it makes is logged.
For Agents
Create and send purchase orders, receive items, upload and code vendor bills, run three-way matches, and approve procurement workflow steps in Saldor.
Use for: I need to raise a purchase order for new laptops, Upload this vendor invoice PDF and match it to the right PO, Find all bills from one vendor filtered by status, Approve the workflow step waiting on me
Not supported: Does not move money, keep a general ledger, or file taxes. Use for procure-to-pay purchasing, receiving, bill matching, and approvals only.
The Saldor API runs a procure-to-pay workflow: purchase requests and orders, item receipts, vendor bills, and three-way matching between them. It onboards and approves vendors with their payment, tax, and compliance details, runs sourcing events with RFX questionnaires and quote comparison, and tracks contracts, blanket agreements, and renewals. Approval workflows, budgets and spend reports, GL account and project coding, inventory and BOM records, and a Brex Bill Pay hand-off round out the surface, with every response wrapped in a data envelope.
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>