Credentials and tokens

There are two different kinds of access here, and most paths need little or nothing. This page lists every test value in one place: nothing to request from anyone, no other page to visit.

Surface	What it needs	Where it comes from
Docs MCP (remote)	nothing	Public, …/mcp, no token.
The sandbox API (build a client)	an api_key + an integration id	Pre-loaded demo creds or install fixtures, all listed below.
Procurement MCP (remote)	a shared demo token	Public, published below; a gate, not auth (explained in full there).

You can do a lot with zero secrets

Connect the Docs MCP (public, no token), or call the API with the pre-loaded demo credentials below. Neither needs anything from anyone.

1. API credentials, to build a client

Every API call (except the install call) carries two headers:

Authorization: Bearer <api_key>
Partly-Integration-ID: <integration_id>

There are two ways to get a valid pair, both fully self-serve, nothing to request from anyone.

Pre-loaded demo credentials

The sandbox ships two ready-to-use credentials wired to the seeded Corolla job. Copy a pair and make an authenticated call immediately, no signup, no install:

Role	Authorization: Bearer	Partly-Integration-ID
Repairer (drives the lifecycle)	partifact_demo_repairer_3f8a1c0d9e2b4a67b1c2	0c000000-0000-4000-8000-000000000001
Supplier (confirms orders)	partifact_demo_supplier_8b4e2f1a6c0d3e9f7a25	0c000000-0000-4000-8000-000000000002

curl -s https://partifact-mock.thanhvuttv.workers.dev/api/2026-01/repairer.jobs.get \
  -H "Authorization: Bearer partifact_demo_repairer_3f8a1c0d9e2b4a67b1c2" \
  -H "Partly-Integration-ID: 0c000000-0000-4000-8000-000000000001" \
  -H "Content-Type: application/json" \
  -d '{"identity":{"external":"CCC-2026-04817"}}'

Provision your own (the install flow)

A real integration shouldn’t run on hand-pasted keys. The install call (integrations.insert) exchanges an OAuth grant for a fresh api_key + integration_id. The grant fixtures are seeded, so you can run the handshake yourself:

Grant field	Value
client_id	partifact_client_demo
client_secret	secret_demo_8f3a
access_code	ac_demo_valid_15m (single-use)

Watch the flow in action

These are all the values you need. Authentication is the demonstration: the live install handshake (request plus the fresh credential it returns), the four rejections that prove the gate is real, and exactly what’s simplified versus production.

2. The Procurement MCP demo token, to connect the hosted endpoint

This is a gate, not authentication

This token is not the API’s auth contract; it is a lightweight, published gate on the hosted demo endpoint so the free-tier sandbox isn’t swamped, and it may be rate-limited or rotated. Every connection still gets its own fully isolated slot (Authentication is the real install flow).

The public demo token is:

partifact-public-demo

Paste it into the connect URL and pick any <your-slot> for a private sandbox:

https://partifact-procurement-mcp.thanhvuttv.workers.dev/mcp/partifact-public-demo/<your-slot>

Or send it as a header (Authorization: Bearer partifact-public-demo) with <your-slot> in the path. See Procurement MCP for the slot model.

Prefer no token at all?

• Read the docs as tools → the public Docs MCP (no token).
• Build a client → use the demo API credentials above, or the install flow.

What each setup path actually needs

claude.ai connector

Docs MCP: just the URL. Procurement MCP: the URL with the public demo token plus your slot. → Connect Claude

Claude Desktop / Code

The same deployed URLs: paste into the Desktop connectors UI, or claude mcp add --transport http in Claude Code. Nothing to build.