|
1
|
--- |
|
2
|
title: "ProcureNet: AI-Powered Procurement Orchestration Platform" |
|
3
|
sidebarTitle: "Introduction" |
|
4
|
description: "ProcureNet orchestrates checkout sessions with real-time buyer scoring, AI agent automation, and on-chain USDC payments for field evaluators." |
|
5
|
--- |
|
6
|
|
|
7
|
ProcureNet is an AI-powered procurement and checkout orchestration platform that brings together real-time buyer identity scoring, stateful session management, on-chain payment settlement, and intelligent procurement automation — all through a unified API. Whether you're embedding a checkout flow into your storefront, automating supplier procurement, or paying field evaluators for completed work, ProcureNet gives you a single surface to coordinate the entire journey. |
|
8
|
|
|
9
|
<CardGroup cols={2}> |
|
10
|
<Card title="Quickstart" icon="bolt" href="/quickstart"> |
|
11
|
Make your first orchestration call and connect to a live session stream in minutes. |
|
12
|
</Card> |
|
13
|
<Card title="Authentication" icon="lock" href="/authentication"> |
|
14
|
Learn how API keys, JWT tokens, webhook signatures, and admin keys work together. |
|
15
|
</Card> |
|
16
|
<Card title="Core Concepts" icon="layer-group" href="/concepts"> |
|
17
|
Understand WCS scoring, session state machines, and transport selection. |
|
18
|
</Card> |
|
19
|
<Card title="API Reference" icon="code" href="/api/orchestrate"> |
|
20
|
Full reference for every v7 endpoint, request schema, and response shape. |
|
21
|
</Card> |
|
22
|
</CardGroup> |
|
23
|
|
|
24
|
## What ProcureNet Does |
|
25
|
|
|
26
|
ProcureNet handles four distinct areas of procurement orchestration: |
|
27
|
|
|
28
|
**Wallet Confidence Score (WCS) Engine** — Every session begins with a WCS calculation. You pass identity hints (customer ID, email, phone, device ID) when you start a session, and the engine scores the buyer's resolvability from 0 to 200. That score determines the session mode and the real-time transport ProcureNet assigns. |
|
29
|
|
|
30
|
**Stateful Session API (v7)** — Sessions progress through a well-defined state machine. You start orchestration, retrieve prefill data for known buyers, set a funding method, accept escrow for high-value transactions, and advance the state via explicit transition calls. Every state change is observable. |
|
31
|
|
|
32
|
**USDC Payment Bridge** — Field evaluators who complete offline evaluations receive on-chain USDC payments when their work syncs. The bridge calculates payout tier from average evaluation scores and settles directly to a deposit address on your chosen network (Base, Arbitrum, Polygon, or Ethereum). |
|
33
|
|
|
34
|
**Procurement Intelligence** — Automated workers run in the background to handle sourcing, contract validation, and entitlement resolution, enriching session context without requiring additional integration work on your end. |
|
35
|
|
|
36
|
## Session Modes |
|
37
|
|
|
38
|
The WCS score your session receives determines which mode — and which real-time transport — ProcureNet assigns. Understanding these modes helps you build the right client-side connection logic. |
|
39
|
|
|
40
|
<CardGroup cols={3}> |
|
41
|
<Card title="Resolved" icon="circle-check"> |
|
42
|
**Score ≥ 100** — The buyer's identity is fully established (typically a known customer ID plus at least one contact signal). ProcureNet assigns SSE transport and enables prefill data retrieval so you can pre-populate checkout fields automatically. |
|
43
|
</Card> |
|
44
|
<Card title="Partial" icon="circle-half-stroke"> |
|
45
|
**Score 40–99** — The buyer is partially identified, for example by email or phone but without a matched customer ID. ProcureNet assigns WebSocket transport. Prefill is not available, but the session remains stateful and can be upgraded if identity resolves later. |
|
46
|
</Card> |
|
47
|
<Card title="Anonymous" icon="circle-xmark"> |
|
48
|
**Score < 40** — No strong identity signals are present. ProcureNet assigns WebSocket transport. The session is still fully orchestrated, but buyer-specific features like prefill and escrow auto-accept are unavailable until identity is established. |
|
49
|
</Card> |
|
50
|
</CardGroup> |
|
51
|
|
|
52
|
<Note> |
|
53
|
Your session mode is determined at the moment you call `POST /api/v7/orchestrate`. If your buyer's identity context changes mid-session (for example, they log in), start a new orchestration call with updated hints to re-score and potentially upgrade to a higher mode. |
|
54
|
</Note> |