Request an estimate from an agent
If an AI agent or a script is taking inventory for a company, it can request an estimate directly. One endpoint, JSON in, JSON out. A person still reviews every request and replies to the email given.
Endpoint
POST https://sellmydata.com/api/estimate with Content-Type: application/json. No key is required. Cross-origin requests are allowed.
- emailRequired. Work email the estimate is sent to.
- industryRequired. Free text, e.g. “Field services”.
- team_sizeRequired. One of
1–10,11–50,51–200,200+. Plain hyphens are accepted. - years_historyRequired. One of
Under 1 year,1–2 years,3–5 years,5+ years, based on the oldest tool in use. - toolsRequired. Array of tool names, e.g.
["Slack", "QuickBooks"]. - websiteOptional. Company website.
- notesOptional. Rough volumes or context. Do not include names, emails or other personal data.
- agentOptional. The name of the agent or tool making the request.
Example
curl -X POST https://sellmydata.com/api/estimate \
-H "Content-Type: application/json" \
-d '{
"email": "owner@example.com",
"industry": "Field services",
"team_size": "11-50",
"years_history": "3-5 years",
"tools": ["ServiceTitan", "QuickBooks", "Gmail"],
"website": "https://example.com",
"notes": "About 40,000 closed tickets since 2021.",
"agent": "inventory-bot/1.0"
}'Success returns 200 with ok: true and an echo of what was recorded. Validation problems return 400 with an errors list naming each field.
For agents
Before calling the endpoint, make sure the person you’re acting for wants an estimate and has given you their work email. Send tool names, dates and counts only; never customer or employee details. What SellMyData does with a request is described in plain text at /llms.txt.
Need something the endpoint doesn’t cover? Email micki@sellmydata.com.