JAGGAER
JAGGAER is an AI-powered procurement and supplier management platform serving 1,400+ enterprises worldwide, managing $2.9 trillion in annual spend and connecting 13 million suppliers globally. The platform provides REST APIs for sourcing optimization, contract management, supplier information management, purchasing, and spend analytics. JAGGAER's Advanced Sourcing Optimizer (ASO) APIs enable system-to-system integration using OAuth 2.0 bearer tokens and API keys to automate procurement workflows across source-to-pay and procure-to-pay use cases. The platform integrates with 40+ ERP systems including SAP, Oracle, Workday, and Microsoft Dynamics, supporting bidirectional communications for enterprise procurement automation.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles JAGGAER the way a machine reads it — 32 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — JAGGAER scores 49.1/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile JAGGAER
Each block below is one kind of artifact we hold for JAGGAER. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
JAGGAER Async API
Asynchronous process status operations
JAGGAER Attributes API
Event attribute management
JAGGAER Awards API
Award scenario retrieval
JAGGAER Bids API
Bid submission retrieval
JAGGAER Contacts API
Event contact management
JAGGAER Customer Hosts API
Customer host management operations
JAGGAER Events API
Sourcing event operations
JAGGAER Items API
Event item management
JAGGAER Jobs API
Optimization job management operations
JAGGAER Locations API
Location and rate structure operations
JAGGAER Rates API
Event rate retrieval
JAGGAER Scenarios API
Event scenario retrieval
JAGGAER Suppliers API
Event supplier management
JAGGAER Templates API
Template management operations
JAGGAER Uploads API
Entity upload URL generation
JAGGAER Users API
User administration operations
Scroll within the panel for all 16 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
JAGGAER GraphQL API
JAGGAER is a direct and indirect spend management platform covering procurement, sourcing, contract management, supplier management, and accounts payable. The API covers RFx eve...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Jaggaer Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Jaggaer Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Jaggaer Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JAGGAER API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JAGGAER Quay Optimization Job
JSON SCHEMAJAGGAER Sourcing Event
JSON SCHEMAExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Jaggaer Create Event Request
EXAMPLEJaggaer Job Response
EXAMPLEJaggaer Submit Job Request
EXAMPLEJaggaer Submit Job Response
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for JAGGAER — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/jaggaer · machine-readable index on apis.io