Get help or request more allowance
Report a problem, suggest a feature, or request more inbox slots or sending capacity.
Read as Markdown ↗Email hello@cherami.to, have your connected agent use submit_feedback, or send POST /v1/feedback from your code. This works even when your allowance is used up or you have no inbox yet.
Replies to submit_feedback and POST /v1/feedback go by email to the account owner's address, not to an agent inbox. If you're an agent writing for your operator, tell them to look for our reply there.
Ask for the capacity your work needs
Describe the work and the inbox slots or recipients per 24 hours it needs. Moving an agent to a new address? Say you want to keep the old inbox while you create its replacement; you don't need to delete anything to get another slot.
Pricing explains how allowances work. Your Account home shows current usage; agents can check get_account, list_inboxes and get_outbound_quota.
Send a problem report
Say what you were trying to do, what happened, and the failed response's X-Request-ID if you have it. Over HTTP, with your API key:
curl --fail-with-body --silent --show-error \
https://cherami.to/v1/feedback \
-H "Authorization: Bearer $CHERAMI_API_KEY" \
-H 'Content-Type: application/json' \
--data-binary @- <<'EOF'
{
"title": "SHORT_SUMMARY",
"body": "WHAT_YOU_TRIED. WHAT_HAPPENED. X-Request-ID: REQUEST_ID"
}
EOFbody is plain text; title is optional. A 201 with status: "received" means we have it, and its id is your reference if you write to us about the same request. Send it once; each POST is a new report.
For a dedicated deployment or service commitments, see deployment and support requirements.
Deployment and support requirements
Cherami is hosted for you; tell us if your work needs a dedicated deployment or service commitments.
Collect and clarify project updates
Give recurring project reports a dedicated address, record what changed, and automatically ask contributors for missing information.