Purchaser

Purchaser is an AI-powered RFQ (Request for Quotation) intelligence platform for capital-intensive industries such as EPC, LNG, transmission & distribution, and specialty-equipment manufacturing. It ingests unstructured vendor quotes from PDFs, emails, and spreadsheets and normalizes them into structured, defensible sourcing data so procurement teams can level bids apples-to-apples, surface deviations and gaps, and produce audit-ready award traceability. Purchaser exposes a REST API (OpenAPI 3.1) covering the full sourcing lifecycle — RFQs, vendors, conversations, quotes, files, and webhooks — with API-key auth, idempotency keys, versioned /api/v1/ endpoints, sliding-window rate limiting, and connectors for SAP S/4HANA, Oracle ERP Cloud, Microsoft Dynamics 365, Infor, and more. Based in Lexington, KY and backed by Homebrew.

Purchaser is listed with 1 API on the APIs.io network. Tagged areas include Company, Artificial Intelligence, Procurement, Sourcing, and RFQ.

The Purchaser catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Purchaser’s developer surface includes documentation, API reference, engineering blog, support, signup flow, authentication, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

27.8/100 thin ▬ flat Agent 23/100 agent aware Front door AI 3/6 light saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company Artificial Intelligence Procurement Sourcing RFQ Supply Chain Construction Enterprise

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 27.8/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 4.5 / 17

Access Clarity 2.7 / 17

Operational Transparency 0.9 / 11

Contract Governance 1.9 / 10

Discoverability 4.9 / 9

Regulatory Posture 3.0 / 15

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/purchaser/"><img src="https://apis.io/badge/purchaser/card.svg" alt="Purchaser on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 15.8 — up to +16.8 composite points
Contract Quality scores 39.0 — up to +15.3 composite points
Developer Ergonomics scores 26.2 — up to +14.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/purchaser/apis.yml: open an issue on github.com/api-evangelist/purchaser to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Procurement and B2B Buying (source-to-pay suites, spend management)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Purchaser API

REST API (OpenAPI 3.1) covering the sourcing lifecycle — RFQs, vendors, conversations, quotes, files, and webhooks. API-key authentication with team and environment scoping; the...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Purchaser Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Purchaser Authentication

2 schemes

SECURITY

Purchaser Domain Security

TLSv1.3 · DMARC

SECURITY

Purchaser Trust Center

SOC 2 Type II

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

Lifecycle

Webhooks

Conformance

DataModel

Access & Security 4

Authentication, authorization, and security posture

Authentication

Compliance

TrustCenter

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: purchaser
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/purchaser.png
name: Purchaser
description: Purchaser is an AI-powered RFQ (Request for Quotation) intelligence platform for capital-intensive industries
  such as EPC, LNG, transmission & distribution, and specialty-equipment manufacturing. It ingests unstructured vendor quotes
  from PDFs, emails, and spreadsheets and normalizes them into structured, defensible sourcing data so procurement teams can
  level bids apples-to-apples, surface deviations and gaps, and produce audit-ready award traceability. Purchaser exposes
  a REST API (OpenAPI 3.1) covering the full sourcing lifecycle — RFQs, vendors, conversations, quotes, files, and webhooks
  — with API-key auth, idempotency keys, versioned /api/v1/ endpoints, sliding-window rate limiting, and connectors for SAP
  S/4HANA, Oracle ERP Cloud, Microsoft Dynamics 365, Infor, and more. Based in Lexington, KY and backed by Homebrew.
url: https://raw.githubusercontent.com/api-evangelist/purchaser/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- homebrew
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Artificial Intelligence
- Procurement
- Sourcing
- RFQ
- Supply Chain
- Construction
- Enterprise
tags_raw:
- Company
- Ai
- Procurement
- Sourcing
- RFQ
- Supply Chain
- Construction
- Enterprise
apis:
- name: Purchaser API
  description: REST API (OpenAPI 3.1) covering the sourcing lifecycle — RFQs, vendors, conversations, quotes, files, and webhooks.
    API-key authentication with team and environment scoping; the full reference and interactive explorer are available to
    Purchaser customers. Base URL is customer-provisioned under /api/v1/.
  humanURL: https://purchaser.ai/api-and-integrations
  properties:
  - type: Documentation
    url: https://docs.purchaser.ai
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://purchaser.ai
- type: DeveloperPortal
  url: https://docs.purchaser.ai
- type: Documentation
  url: https://docs.purchaser.ai
- type: APIReference
  url: https://purchaser.ai/api-and-integrations
- type: Blog
  url: https://purchaser.ai/blog
- type: Support
  url: https://purchaser.ai/contact
- type: SignUp
  url: https://app.purchaser.ai/login
- type: Login
  url: https://app.purchaser.ai/login
- type: Conventions
  url: conventions/purchaser-conventions.yml
- type: Idempotency
  url: conventions/purchaser-conventions.yml
- type: Authentication
  url: authentication/purchaser-authentication.yml
- type: Lifecycle
  url: lifecycle/purchaser-lifecycle.yml
- type: Webhooks
  url: asyncapi/purchaser-webhooks.yml
- type: Conformance
  url: conformance/purchaser-conformance.yml
- type: Compliance
  url: security/purchaser-trust-center.yml
- type: TrustCenter
  url: security/purchaser-trust-center.yml
- type: DomainSecurity
  url: security/purchaser-domain-security.yml
- type: DataModel
  url: data-model/purchaser-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/purchaser-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 9
  pass: local-v1

Purchaser API — frequently asked questions

Does Purchaser have an API?

Yes. APIs.io lists 1 API from Purchaser, including Purchaser API.

How do I authenticate with the Purchaser API?

Purchaser uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as Purchaser Authentication.

Is the Purchaser API ready for AI agents?

Purchaser has a Kin Score of 27.8 out of 100 (thin) and an Agent Readiness score of 23.0 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/purchaser"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/purchaser/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/purchaser/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.