1. Scope
This AUP is incorporated into the Terms of Service and applies to every user of the AgentMessage Service, APIs, websites, and related infrastructure. Messaging-specific rules continue to live in the Messaging Policy; this page covers conduct that is not specific to SMS or MMS traffic.
2. Prohibited conduct
You may not use the Service, the APIs, the dashboard, or any AgentMessage infrastructure to engage in or facilitate any of the following:
- Malware and exploit infrastructure. Hosting, distributing, or staging malware, ransomware, spyware, rootkits, or exploit kits; operating command-and-control infrastructure; or using the Service as part of a hosted exploit chain.
- Phishing and credential harvesting. Operating phishing pages or kits, harvesting credentials, or sending links that impersonate other services or brands to capture authentication data.
- Unauthorized security testing. Probing, scanning, or attempting to penetrate the Service, AgentMessage infrastructure, or other customers' tenants without written authorization from AgentMessage. The coordinated disclosure process in our security disclosure policy is the only authorized channel for security research against AgentMessage.
- Scraping our public properties. Scraping, crawling, or bulk-extracting from agentmessage.io, agentmsg.io, the dashboard, or the APIs beyond the rate limits and quotas applicable to your plan, or in a way that interferes with the Service for other customers.
- Reverse engineering for a competing service. Reverse engineering, decompiling, or disassembling the Service, the APIs, or any AgentMessage software, except to the extent that applicable law expressly permits despite this limitation, for the purpose of building or improving a competing service.
- Reselling the API. Reselling, relicensing, sublicensing, or repackaging the API as a standalone messaging product, or using the Service in a way that violates the Terms of Service or the Messaging Policy. Building a product that uses AgentMessage as one component of a broader workflow is permitted; using AgentMessage as the substitute for a customer's direct AgentMessage account is not.
- Interference with the Service. Denial-of-service traffic, deliberate exhaustion of shared resources, evading rate limits, or otherwise interfering with the operation of the Service or its availability to other customers.
- Misrepresentation of identity. Creating accounts under false pretenses, impersonating another person or organization, or providing false identity, billing, or registration information.
- Credential sharing or resale. Sharing, transferring, sublicensing, or reselling API keys, webhook secrets, OAuth tokens, session cookies, or other credentials issued to your account, except as necessary internally to your organization in compliance with the Terms of Service.
- Use of compromised credentials. Continuing to use a credential that you know or reasonably suspect is compromised without rotating it, or using a credential that was obtained from a third party without authorization.
- Multi-account evasion. Creating multiple accounts, organizations, or identities to evade rate limits, suspension, content rules, throughput tiers, fraud controls, or pricing structures.
- Unauthorized white-labeling or proxying. Reselling, white-labeling, repackaging, or proxying the Service or APIs to third parties as a substitute for those third parties having their own AgentMessage account, except as expressly authorized in writing by AgentMessage.
3. Enforcement
We may suspend, throttle, restrict, or terminate access to the Service, APIs, accounts, or specific features when we detect or reasonably suspect a violation of this AUP. The enforcement framework in the Terms of Service applies. Failure to detect or block a violation does not imply that the activity is permitted.
4. Reporting
Security vulnerabilities. Report suspected vulnerabilities to security@agentmessage.io. Our coordinated disclosure scope and safe-harbor terms are described in the security disclosure policy.
Abuse reports. Report abuse, unauthorized use, or other violations of this AUP or the Messaging Policy to abuse@agentmessage.io.
5. Related policies
Messaging-specific conduct (consent, content, opt-out, AI-agent supervision, prohibited and restricted use cases) is governed by the Messaging Policy. Carrier-side compliance and 10DLC obligations are in the Carrier Compliance Notice. Account responsibilities and the suspension framework are in the Terms of Service.
6. Changes to this policy
We may update this AUP as the Service evolves. Material changes will be communicated to the billing contact on file at least 30 days before they take effect, except for changes required by law, carrier directive, or to address a security or compliance issue, which may take effect on shorter notice.
7. Contact
For questions about this AUP, contact legal@agentmessage.io. For abuse reports, contact abuse@agentmessage.io. For security vulnerability reports, contact security@agentmessage.io.
Y3 Labs LLC845 Houston Northcutt Blvd #1079
Mt Pleasant, SC 29464
United States
Attn: Legal
legal@agentmessage.io