P3 Lending Developer API

B2B API for reputation scores. Base URL: https://api.p3lending.space

Quickstart

1. Log in to p3lending.space, open Developers in the sidebar.
2. Create an API key (copy it once; it won’t be shown again).
3. Call the API with Authorization: Bearer <your_key>.

curl -H "Authorization: Bearer p3_live_..." \
  "https://api.p3lending.space/api/v1/reputation/score?user_id=UUID"

Auth

All /api/v1/* endpoints require an API key in the Authorization header:

Authorization: Bearer p3_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
# or
Authorization: Bearer p3_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Keys are scoped (e.g. score:read, score:history). Never store or log the raw key; store only the prefix if needed for display.

Plans

Start in Sandbox with test keys. Upgrade to Paid to use live keys and higher quotas.

Plan	Key prefix	Default limits	Notes
Sandbox (Free)	p3_test_...	10 rpm · 500 rpd · 5,000 / month	Testing and integration
Paid (Production)	p3_live_...	120 rpm · 50,000 rpd · 1,000,000 / month	Live usage, higher quotas

Upgrade: email founders@p3lending.space.

Endpoints

• GET /api/v1/reputation/score?user_id= — Score by user ID (scope: score:read).
• GET /api/v1/reputation/score/by-wallet?address= — Score by wallet address (scope: score:read).
• POST /api/v1/reputation/score/batch — Body: {"user_ids": ["uuid1", "uuid2"]} (scope: score:read).
• GET /api/v1/reputation/score/history?user_id=&from=&to= — Score history (scope: score:history).

OpenAPI spec: /docs/openapi.json.

Scoring model (Phase 1)

Scores are now returned on a 0-1000 scale with explainability fields:

• trust_score, risk_score, capacity_score
• reputation_score (same value as score for backward compatibility)
• top_reasons_positive, top_reasons_negative, missing_data, caps_applied

Bands: A (850+), B (700-849), C (550-699), D (400-549), E (<400).

Guardrail caps can lower the final score: no history cap (650), no KYC cap (700), new account cap (600), and recent default cap (450).

Errors

Responses use HTTP status codes and a JSON body:

• 400 — Bad request (e.g. missing user_id).
• 401 — Invalid or missing API key.
• 403 — Valid key but missing required scope.
• 404 — User not found.
• 402 — Paid plan required for live keys (code=paid_required).
• 429 — Rate limit exceeded (X-RateLimit-*) or monthly quota exceeded (code=monthly_quota_exceeded).
• 503 — Developer API not configured.

Rate limits

Per-key limits (configurable when creating the key):

• X-RateLimit-Limit — Requests per minute.
• X-RateLimit-Remaining — Remaining in current window.
• X-RateLimit-Reset — Unix timestamp when the window resets.

Monthly quota headers:

• X-MonthlyQuota-Limit — Requests allowed in the current period.
• X-MonthlyQuota-Remaining — Remaining requests.
• X-MonthlyQuota-Reset — Unix timestamp when the period resets.

When exceeded, the API returns 429.