PDF As You Go is in private preview, so support is direct: you reach the team by email and we respond.
Who to email
Section titled “Who to email”| For… | |
|---|---|
| Preview access / onboarding | preview@pdfasyougo.com |
| Help, bugs, and questions | support@pdfasyougo.com |
We typically reply within a couple of business days during preview.
Before you write
Section titled “Before you write”A little context gets you a faster answer:
- Include the
request_idfrom the error response for any failed call — it lets us find the exact request. - Say which surface you’re on — MCP server or HTTP API — and which operation.
- Describe what you expected vs. what happened, with the request body if you can (redact passwords and wallet keys).
- Don’t send secrets. Never include a wallet private key or document passwords in an email.
Common starting points
Section titled “Common starting points”- Payment isn’t completing → Paying with x402 / The 402 flow.
- A call failed → Errors & failures and HTTP API → Errors.
- Questions about cost, wallets, or data → the FAQ.
Feature requests
Section titled “Feature requests”Preview feedback directly shapes what we build — see the Roadmap for current directions, and tell us what you need.