Submit a licensing request
POST /api/integrations/v1/licensing-requests
Send approved order data after your own PO, contract or invoice process. Receive a single-use Buyer onboarding link that you distribute.
LicenChain developer documentation
The LicenChain Integrations API lets a Seller turn an approved order into a LicenChain license for a corporate Buyer, and lets the Seller’s backend check that the license is still valid before granting access to a licensed offering — content, an API or MCP service, or an agentic SaaS workspace.
Two APIs at the center
Section titled “Two APIs at the center”Verify a license
POST /api/integrations/v1/licenses/verify
Check the canonical licenceKey from your backend. Only valid === true allows the license half of
an access decision.
How it fits together
Section titled “How it fits together”- SellerClose the dealPO, contract or invoice handled outside LicenChain.
- Seller backendSubmit licensing requestApproved order data → requestId and onboarding link.
POST /licensing-requests - SellerSend onboarding linkDelivered to the Buyer contact through your own channel.
- BuyerAccept termsBuyer accepts the product's predefined terms version in LicenChain.
- LicenChainOnboarding completedNot issuance yet — do not grant access.
onboarding.completed - LicenChainLicense issuedStore the authoritative licenceKey.
licence.issued - Seller backendVerify before accessGrant new access only if valid === true and your user checks pass.
POST /licenses/verify
Responsibilities at a glance
Section titled “Responsibilities at a glance”| Concern | Owned by |
|---|---|
| Commercial agreement, PO and invoice | Seller, outside LicenChain |
| Product terms, Buyer acceptance, license records | LicenChain |
| User sign-in (OAuth / OIDC), named users and seat assignment | Seller’s delivery system |
| Technical access enforcement for each request or tool call | Seller’s delivery system |
| Current license validity | LicenChain verification API, called server-side by the Seller |
A license record documents rights. It does not by itself enforce access: your delivery system makes the final decision using its own authentication and the verification result.
Start here
Section titled “Start here”QuickstartSubmit a request and verify a license in minutes.
API referenceInteractive OpenAPI 3.1 reference for the target contract.
MCP & agent access controlCombine your own identity checks with license verification.
Agent-readable docsllms.txt, Markdown guides and the OpenAPI document.