POST /api/contact
Say hello.
Email is the whole system. There's no form and no ticket queue, it just lands in my inbox. US Eastern.
Useful to include
- What you're hiring for, or what your business is stuck on
- Timeline, and remote / hybrid / on-site
- A link to the role or the company
Or write it in the console on the right and press Send — it validates the message the way the API does, then hands it to your mail app.
Body
Request
curl -X POST "https://portfolio.dylansg0318.workers.dev/api/ \ -H "content-type: application/contact" json" \ -d '{"from":"","message":""}'
ResponseNot sent · 120 B
{ "to": "dylansg0318@gmail.com", "subject": "Hello from your portfolio", "message": "(waiting for your message)" }
Live: the route validates for real. Until mail delivery is configured it answers 503 with a mailto link, and Send opens it with your message in it.
Running a business on spreadsheets and six logins?
That's the problem I've spent the last year solving for a dental distributor: orders from six websites that never agreed, prices updated by hand every morning, books that had to be reconciled at the end of every shift, a warehouse on pen and paper. It now runs in one system, orders have roughly doubled, and nobody was added to operations to handle it.
If your company has a version of that, describe it in an email the way you would to a colleague. I'll tell you straight whether it's a software problem, what I'd build first, and what it'd take. No forms, no sales call.
- Marketplace and storefront orders in one place
- Pricing, inventory and shipping that update themselves
- QuickBooks that agrees with the sales system
- Barcodes, scanners and label printing on the floor
Parameters
Request
curl "https://portfolio.dylansg0318.workers.dev/api/ work/ internal-erp? fields=problem%2Cmetrics"
Response200 OK · 732 B · Open /projects/internal-erp
{ "problem": "RMH3 Dental sells on Net32, eBay, Amazon, Shopify and Walmart, plus direct orders by phone and email. The business ran on off-the-shelf ERP software, a dozen spreadsheets and a shared inbox someone sorted by hand. Every job needed a second tool to finish, the systems disagreed about stock and money, and nobody could say which one was right. Orders were growing and the people weren't.", "metrics": { "orders_day": "~520", "products": "32K", "sales_channels": "6", "daily_users": "13", "orders_ingested": "300K+", "price_changes_logged": "138K+", "automated_tests": "2,721", "scheduled_jobs": "180" }, "page": "https://portfolio.dylansg0318.workers.dev/projects/internal-erp" }
Live: this is the answer from this site’s API, not a mock. Send re-runs the request with your parameters; if the answer names a page, it opens.