Install Jentic One Beta

Connect the Jaggaer Advanced Sourcing Optimizer (ASO) API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jaggaer Advanced Sourcing Optimizer (ASO) 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%2Fjaggaer.com%2Fjaggaer" | 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%2Fjaggaer.com%2Fjaggaer" | 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 Jaggaer Advanced Sourcing Optimizer (ASO) API.

Create sourcing events from templates for a given customer and user

List and read sourcing events along with their attributes and bids

Create and update event attributes individually or in batches

Submit optimization jobs and track their status to completion

GET STARTED

Start building with Jaggaer Advanced Sourcing Optimizer (ASO) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Jaggaer Advanced Sourcing Optimizer (ASO) API for, with concrete tasks.

★ AI Agent Sourcing Event Creation

An AI agent connected through Jentic stands up a sourcing event from an approved template for a named customer and user, then lists that user's events to confirm it was created. Templates keep the event structure consistent, so the agent can launch repeatable sourcing rounds without rebuilding attributes each time.

Create a sourcing event from a template for a given customer and user, then list the user's events

Optimization Job Orchestration

After bids are collected, an agent submits an optimization job to the Quay service and polls its status until the run finishes, then reads the result. This automates the compute-heavy award step that would otherwise require a user to watch the job in the portal.

Submit an optimization job for an event and poll its status until the run completes

Bid and Award Retrieval

To report sourcing outcomes, an agent retrieves the bids submitted for an event and the awards for the preferred scenario. The async award and bid operations return structured results an agent can summarize for a buyer.

Retrieve the bids for an event and the awards for the preferred scenario

Key Endpoints

26 endpoints — the jaggaer advanced sourcing optimizer (aso) api drives strategic sourcing and procurement optimization across three services.

METHOD

PATH

DESCRIPTION

POST

/oauth2/token

Generate an OAuth 2.0 access token

POST

/chost/{customerHostId}/user/{userId}/template/{templateId}/apiEvent

Create a sourcing event from a template

GET

/chost/{customerHostId}/user/{userId}/apiEvents

List events by user

GET

/event/{eventId}/apiAttributes

List event attributes

POST

/submitJob

Submit an optimization job

GET

/jobStatus/{jobId}

Get optimization job status

GET

/event/{eventId}/apiBids/async

Get bids for an event

POST

/oauth2/token

Generate an OAuth 2.0 access token

POST

/chost/{customerHostId}/user/{userId}/template/{templateId}/apiEvent

Create a sourcing event from a template

GET

/chost/{customerHostId}/user/{userId}/apiEvents

List events by user

GET

/event/{eventId}/apiAttributes

List event attributes

POST

/submitJob

Submit an optimization job

GET

/jobStatus/{jobId}

Get optimization job status

GET

/event/{eventId}/apiBids/async

Get bids for an event

Why Jentic?

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

Setup

Wiring the Jaggaer ASO API by hand means obtaining OAuth 2.0 client-credentials tokens, attaching the API key header, and routing calls across its three service hosts yourself. Through Jentic you install once, import Jaggaer from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Jaggaer puts the customer host id and event id in the URL path (/chost/{customerHostId}/..., /event/{eventId}/...), so a rule can pin your agent to operations on one customer host or event. You choose the operations it may call, so destructive ones like deleting an attribute are not included unless you add them.

Credential isolation

Your Jaggaer OAuth client credentials and API key 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 'create a sourcing event' or 'submit an optimization job', and Jentic returns the matching Jaggaer operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Jaggaer Advanced Sourcing Optimizer (ASO) API through Jentic.

What authentication does the Jaggaer ASO API use?

It uses OAuth 2.0 client-credentials access tokens together with an API key in the `X-API-Key` header, as declared in its OpenAPI spec. You request a token from the token endpoint, then send it with the API key when calling the services. Through Jentic both are stored encrypted by your own Jentic One instance and injected at call time.

Can I submit an optimization job with the Jaggaer ASO API?

Yes. The job-submit operation queues an optimization run for an event, and you can poll the job-status operation and then retrieve the awards for the resulting scenario once it completes.

What are the rate limits for the Jaggaer ASO API?

The OpenAPI spec does not specify rate limits for the Jaggaer ASO API. See the Jaggaer ASO documentation at https://asodocs.jaggaer.com for the current limits that apply to your account.

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

Yes. Write a rule that allows only the event-read and bid-read operations, so the agent can review events and bids but cannot create events, change attributes, or submit optimization jobs, and every call it makes is logged.

How do I create a sourcing event with the Jaggaer ASO API through Jentic?

Search Jentic for 'create a sourcing event', add the Jaggaer ASO API from the directory, and store your OAuth client credentials and API key once. Your agent requests a token, then creates the event from a template. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Jaggaer ASO API MCP server?

You don't need an MCP server to give your agent the Jaggaer ASO API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the event, bid, and optimization-job operations. That keeps extra tool definitions out of the agent's context.

Jaggaer Advanced Sourcing Optimizer (ASO) API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsBusiness Intelligenceoauth2, apiKey26 EndpointsREST

For Agents

Create sourcing events from templates, manage event attributes and bids, submit optimization jobs, and retrieve awarded scenarios.

Use for: Create a sourcing event from a template, List the sourcing events for a user, Get the attributes of a sourcing event, Submit an optimization job for an event

Not supported: Does not handle purchase orders, invoicing, or payment execution. Use for sourcing event management and award optimization only.

The Jaggaer Advanced Sourcing Optimizer (ASO) API drives strategic sourcing and procurement optimization across three services. The customer host service manages customers, users, sourcing events, and templates; the event service works with event attributes, bids, awards, and suppliers; and the Quay service submits and tracks optimization jobs. Agents create events from templates, collect bids, run optimization, and retrieve the awarded scenario.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

45%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

54%

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

68%

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

80%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Jaggaer Advanced Sourcing Optimizer (ASO) API to your agent

Capabilities

Start building with Jaggaer Advanced Sourcing Optimizer (ASO) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jaggaer Advanced Sourcing Optimizer (ASO) API

Jentic AI Readiness Score

Jaggaer Advanced Sourcing Optimizer (ASO) 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