Re:amaze
Re:amaze · Support
Customer support helpdesk, live chat and FAQ
The client pastes their API token from Re:amaze's settings. We store it encrypted.
Building with Re:amaze? The docs have setup steps and code for every tool.
Open the Re:amaze docsTools
Your agent calls any endpoint of Re:amaze's API with the request tool, with the client's access attached.
Base URL for request
https://{brand}.reamaze.io/api/v1
request
HTTPS ANY /v1/clients/{clientId}/reamaze/{path}
Any endpoint of Re:amaze's own API, with the client's access attached.
- servicestringrequired
- This service: reamaze
- methodstringrequired
- GET, POST, PUT, PATCH or DELETE
- pathstringrequired
- The path under https://{brand}.reamaze.io/api/v1
- queryobjectoptional
- Query parameters
- bodyobjectoptional
- A JSON body
Over MCP every tool also takes client_id, from list_clients. Over HTTPS send it as clientId to https://api.operate.as/v1.
What the client approves
- Use the Re:amaze key you paste, with only the access you gave that key
Get started
Send your next client one link
Add a client, select the services, copy the link. You'll get an email the moment their access is ready. Start free, no card required. Paid plans are one flat monthly price, and a busy month never takes your agents offline.