Every masterpiece has a process. Document yours.
Build reviewable records of human contributions, material sources and version relationships as you create. Preserve records for copyright claims and dispute evidence. You guided the AI. Now, claim your credit.
Remote MCP uses HTTPS and your Agent host's browser OAuth flow. Read projects this account may access and records synced by this user; the available scopes also allow viewing or revoking your own Agent connection. No local ZIP is needed.
Remote MCP
Connect the Agent you already use
Your host must support remote MCP over Streamable HTTP and browser-based OAuth authorization with PKCE. Adding a URL in chat or pasting a prompt alone does not install or connect an MCP server.
- Read cloud projects this account is allowed to access.
- Read records already synced by the authorizing user.
- The available connection scopes allow viewing the user's Agent connections and revoking only the connection making the request.
- It cannot access local files or paths, scan, sync, upload originals, modify project data, or widen sharing.
Add the remote server in your host's MCP settings
Remote MCP endpoint: https://portraitpayai.com/api/mcp
If your host cannot add a remote MCP server or cannot complete browser OAuth, use that host's documented MCP configuration path. Tell the user which capability is missing; do not invent settings, OAuth values, client IDs, redirect URIs, commands, or tokens.
Read the machine-readable connection guide →
Need local-folder access? See the advanced local connector guide →
This prompt does not install or configure MCP and contains no token, project ID, password, or local path.
Remote MCP uses HTTPS and your Agent host's browser OAuth flow. Read projects this account may access and records synced by this user; the available scopes also allow viewing or revoking your own Agent connection. No local ZIP is needed.
How It Works
From project materials to a reviewable delivery record
- 1
Organize Materials & Contributions
Bring together scripts, storyboards, AI platform links, and workflow files. Add descriptions of human selection and editing; these are submitted records, not automatic capture of every creative step.
- 2
Confirm a Project Snapshot
The project custodian reviews materials and declarations before sealing a snapshot. File hashes and declaration versions help identify what was included; custodian confirmation is not client acceptance.
- 3
Deliver Work with Reviewable Records
Export a project record package with a PDF summary, file index, integrity manifest, and verification instructions. Signature and timestamp status must be read from the actual package; export alone does not mean external verification succeeded.
Built for Project Delivery
Small AI Video Studios
For teams delivering brand videos and commercial shorts: keep project materials and workflow records together, rather than scattered across production tools.
Independent Producers
For producers responsible for client delivery: organize contributor descriptions, declarations, and the records included in each project snapshot.
Cross-Platform Project Leads
Bring references from different AI tools into one project context. Platform links are supplied references, not verified receipts from those platforms.
Delivery Recipients & Reviewers
Review the exported package using its PDF summary, file hashes, declaration history, and verification instructions. No built-in client approval workflow is promised.
Clear Records. Clear Service Boundaries.
PortraitPay organizes submitted records for review. Asset-level origin declarations, version-linked human contributions, client approvals, and lightweight storage are not yet available as a complete workflow. Third-party timestamps are an optional enhancement, subject to actual integration and verification status. A timestamp is not copyright registration; records do not determine ownership or guarantee dispute outcomes. Comparison tools provide supplementary materials, not infringement findings.
Explore Supplementary Review Tools →