# PlatPhorm Invoices Full Context

Service: platphorm-invoices
Canonical URL: https://invoices.platphormnews.com
Local URL: http://localhost:3000

Role:
PlatPhorm Invoices is a solo-preneur finance operating system. It starts with customer invoicing and adds automation for follow-up, customer memory, assessment conversion, payment-plan suggestions, receipts, reporting, and PlatPhormNews network handoffs.

Data owned:
- Customers
- Invoices
- Invoice line items
- Invoice action artifacts: reminders, payment plans, and receipts
- Automation rules
- Assessment links
- Network handoff previews
- Audit-style state transitions

Current state:
- The app uses deterministic starter data until the first saved invoice mutation.
- Local development writes invoice state to data/invoice-store.local.json.
- Vercel deployments write invoice state to a private Vercel Blob JSON document when Blob is configured.
- Payment processor execution is not configured yet.
- Cross-site dispatch stores one receipt per target and reports ready, accepted, failed, or protected_required from real backend responses.

Public API response shape:
- Success: { "ok": true, "data": {} }
- Error: { "ok": false, "error": { "code": "", "message": "", "details": {} } }

MCP:
- Endpoint: /api/mcp
- Transport: JSON-RPC 2.0
- Methods: initialize, ping, tools/list, tools/call, resources/list, resources/read, prompts/list, prompts/get
- Tools: list_invoices, get_invoice, create_invoice_draft, create_invoice_action, create_invoice_preview, get_platform_status
- Resources: platphorm-invoices://command-center, platphorm-invoices://trust-policy

Auth:
- Use PLATPHORM_API_KEY for every backend service-to-service interaction.
- Accepted protected headers: Authorization: Bearer $PLATPHORM_API_KEY and X-PlatPhorm-API-Key: $PLATPHORM_API_KEY.
- Do not use service-specific platform keys.

Trust policy:
Web dashboard, public-safe discovery, browser-based operations, trusted-domain discovery, standard route compliance, Vercel metadata capture, trace inspection, and agentic workflow discovery are intentionally supported for public read-only debugging and operator workflows. Mutating, administrative, ingestion, replay, fork, remediation, deployment, sync, test-triggering, reporting, and write actions require PLATPHORM_API_KEY.

Canonical discovery sources:
- https://platphormnews.com/api/network/graph
- https://base.platphormnews.com/sitemap-index.xml

PlatPhormNews integrations:
- https://assessments.platphormnews.com for assessment-to-invoice workflows.
- https://docs.platphormnews.com for invoice documentation handoffs.
- https://notes.platphormnews.com for customer memory and invoice follow-up notes.
- https://mcp.platphormnews.com for canonical MCP capability registration.
- https://platphormnews.com for root graph and network topology discovery.