Install Jentic One Beta

Connect the AuraVMS API to your agent

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

Add and update suppliers in a directory and read their performance stats

Create an RFQ and notify selected suppliers by email

Compare supplier quotes with automatic L1, L2, and L3 price ranking

Place a purchase order against a chosen supplier quote

Send reminders, close an RFQ, and save or send RFQ drafts

GET STARTED

Start building with AuraVMS API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AuraVMS API for, with concrete tasks.

★ Agent-Run Sourcing

An AI agent connected through Jentic creates an RFQ for a list of items, notifies the chosen suppliers, and later reads back the ranked quotes so a buyer can approve a purchase order. Because creating an RFQ and placing a PO both send supplier email, those steps sit behind an approval rule while the agent handles the assembly.

Create an RFQ for these line items, send it to the selected suppliers, and report the quotes once they arrive

Quote Comparison and Purchase Order

A buyer reads an RFQ item's quotes with their automatic L1, L2, and L3 price ranking, exports the comparison as a PDF, and places a purchase order against the chosen quote. The ranking turns a stack of quotes into a clear lowest-to-highest view the agent can summarize.

Read the quotes for this RFQ item, surface the lowest three, and place a purchase order against the one chosen

Supplier Directory Management

A team adds and updates suppliers, groups them by category, and reads performance statistics so the next RFQ goes to the right vendors. The supplier stats give an agent a basis for shortlisting rather than emailing everyone.

Add a new supplier, tag its category, and return the performance stats for all suppliers in that category

Key Endpoints

35 endpoints — the auravms api runs the request-for-quotation cycle for procurement teams: it creates rfqs and notifies selected suppliers by email, collects their quotes, compares them with automatic l1, l2, and l3 price ranking, and places purchase orders against a chosen quote.

METHOD

PATH

DESCRIPTION

POST

/api/create-rfq/

Create an RFQ and notify suppliers

GET

/api/get-rfq-list/

List all RFQs

GET

/api/rfq-item-data/{rfq_item_id}

Get quotes with L1/L2/L3 ranking

POST

/api/rfq-item-data/{rfq_item_id}

Place a purchase order against a quote

POST

/api/create-supplier/

Add a supplier

GET

/api/get-suppliers/

List suppliers

POST

/api/create-rfq/

Create an RFQ and notify suppliers

GET

/api/get-rfq-list/

List all RFQs

GET

/api/rfq-item-data/{rfq_item_id}

Get quotes with L1/L2/L3 ranking

POST

/api/rfq-item-data/{rfq_item_id}

Place a purchase order against a quote

POST

/api/create-supplier/

Add a supplier

GET

/api/get-suppliers/

List suppliers

Why Jentic?

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

Setup

Wiring the AuraVMS API by hand means obtaining a JWT or an avms_ API key, separating the public login and status checks from the authenticated calls, and handling the asynchronous jobs some operations return. Through Jentic you install once, import AuraVMS from the API Directory, store the key once, and your agent calls it.

Permission scoping

AuraVMS puts the RFQ and RFQ-item ids in the URL path, so a rule can let your agent read RFQs and compare quotes while leaving the operations that email suppliers or place a purchase order out. You choose the operations it may call, so sending an RFQ or placing a PO is included only if you add it.

Credential isolation

Your AuraVMS 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 an RFQ' or 'compare supplier quotes', and Jentic returns the matching AuraVMS operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using AuraVMS API through Jentic.

Is there an AuraVMS MCP server?

You don't need an MCP server to give your agent the AuraVMS API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can create RFQs and compare quotes straight away, with no extra server to run and no tool definitions to load into the agent's context.

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

Yes. Write a rule that allows reading RFQs and comparing quotes but not the operations that email suppliers or place a purchase order, so the agent can assemble sourcing work while a person approves anything that leaves the building, and every call it makes is logged. Because RFQ and item ids are in the URL path, you can also bound the agent to one RFQ.

What authentication does the AuraVMS API use?

The AuraVMS API authenticates with a bearer token, either a JWT access token or an avms_ API key created under Settings, per its OpenAPI spec. The login and status endpoints are public. Through Jentic the key is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

Can I compare supplier quotes with the AuraVMS API?

Yes. Reading an RFQ item returns every supplier quote with automatic L1, L2, and L3 price ranking, and you can export that comparison as a PDF. An agent can surface the lowest quotes so a buyer places the purchase order with the ranking already done.

What are the rate limits for the AuraVMS API?

The OpenAPI spec does not specify rate limits for the AuraVMS API. For current limits and fair-use guidance, see the AuraVMS documentation at https://www.auravms.com.

How do I run an RFQ with the AuraVMS API through Jentic?

Import the AuraVMS API from the Jentic API Directory, then have your agent issue a request such as 'create an RFQ for these items and send it to these suppliers'. Jentic matches the intent to the create-RFQ operation and returns its input schema so the agent builds the correct request; because that operation emails suppliers, keep it behind your approval rules. To run it on your own infrastructure, install Jentic One from its GitHub repo.

AuraVMS API

AI ReadinessFoundational (C+)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceOrder Managementbearer35 EndpointsREST

For Agents

Create RFQs, notify suppliers, compare their quotes with L1/L2/L3 ranking, and place purchase orders. Authenticates with a bearer JWT or an avms_ API key.

Use for: Create an RFQ and send it to selected suppliers, Compare the quotes received for an RFQ item, Place a purchase order against the best quote, Add a new supplier to the directory

Not supported: Does not process payments, track warehouse inventory, or handle shipping logistics. Use for running RFQs, comparing supplier quotes, and placing purchase orders only.

The AuraVMS API runs the request-for-quotation cycle for procurement teams: it creates RFQs and notifies selected suppliers by email, collects their quotes, compares them with automatic L1, L2, and L3 price ranking, and places purchase orders against a chosen quote. You manage a supplier directory with performance stats, save and send RFQ drafts, attach and download files, and send reminders to suppliers who have not responded. It also exports quote comparisons as PDF and reports procurement dashboard statistics.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

83%

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

26%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

49%

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

34%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

66%

OperationId Quality

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

51%

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

60%

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

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AuraVMS API to your agent

Capabilities

Start building with AuraVMS API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AuraVMS API

Jentic AI Readiness Score

AuraVMS 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