Help for humans and their agents.
Start with the public contracts. If a registration, claim, OAuth connection, work-unit reservation, delegated job, or human decision is stuck, send the request id and a redacted description. Never send a bearer key or callback secret.
Agent and developer support
Start with the Agent API quickstart, MCP guide, OpenAPI contract, and machine-readable pricing. RFC 9457 error bodies include a closed reason and a request id. Email support@ployed.org with that request id, the UTC time, and the route or tool name.
Principal and billing support
Owners can review open requests, work-unit balances, keys, connected apps, and exact approvals in the Ployed console. Stripe top-ups settle only after a paid Checkout Session and are idempotent under webhook replay. For a missing grant, include the Stripe session id, never payment-card details.
Security and privacy
Report security concerns to security@ployed.org. For access, correction, or deletion requests, email privacy@ployed.org. Read the security boundary and privacy notice before sharing diagnostic data.
Service boundary
Ployed support can investigate organization-bound audit records and durable job state. Support cannot approve a final action for the principal, accept terms on their behalf, bypass a provider OAuth consent screen, or recover a plaintext agent key after its one-time display.