This is the same agreement that governs the ListingPro app (pro.movingletters.ai) and the ListingPro API. This page shows the current version.
These API & Webhook Terms ("API Terms") are an addendum to the Data License Agreement ("DLA") between you and iServices Inc., doing business as Moving Letters AI ("we", "us"). They apply in addition to the DLA and our Terms of Service. Capitalized terms not defined here have the meanings in the DLA.
How API, MCP and webhook data may be used. Everything you build with our API, MCP access or webhooks is your responsibility and must comply with the law, and unlawful automated contact is not permitted. We do not condone, recommend or endorse automated calling, texting or emailing of homeowners or other consumers identified in our data; any automated contact with realtors or agents must comply with CAN-SPAM, the TCPA and do-not-call rules. The DLA's informational-only, no-consent, own-risk, indemnity and suspension terms apply in full to every record delivered programmatically.
1. Scope
1.1 These API Terms govern your use of: (a) API keys and the ListingPro / Moving Mailers REST API; (b) MCP credentials and any access by AI agents, assistants or tools acting for you ("AI-Agent Access"); and (c) webhooks we send to endpoints you configure (together, the "Developer Services").
1.2 Acceptance. You must accept these API Terms when you create an API key, MCP credential or webhook. By creating, holding or using any of them, you agree to these API Terms on behalf of yourself and the company you represent, and you represent that you have authority to do so.
2. Credentials
2.1 Confidential. API keys, MCP credentials, webhook signing secrets and tokens ("Credentials") are confidential. Do not embed them in client-side code, public repositories, shared documents or prompts visible to third parties.
2.2 You are liable for all use. You are responsible for all activity under your Credentials, whether or not authorized by you, including activity by AI agents, automations, contractors and integrations you connect.
2.3 Rotate and revoke. If you suspect a Credential has been exposed or compromised, revoke or rotate it immediately in the dashboard and notify us under Section 7. We may revoke or rotate any Credential at any time for security reasons.
3. Rate Limits and Fair Use
3.1 We set rate limits, quotas and record limits, which may vary by plan and change over time. You will not attempt to exceed or circumvent them, including by using multiple accounts or keys.
3.2 We may throttle, queue, limit or suspend Developer Services at any time to protect the platform, our data sources or other customers, or where usage appears excessive, abnormal or inconsistent with your plan.
4. Webhooks
4.1 No delivery guarantee. Webhook delivery is best-effort. Events may be delayed, delivered out of order, delivered more than once, or not delivered. We may retry failed deliveries; your endpoint must handle duplicates idempotently.
4.2 Verify signatures. You must verify the signature on every webhook using your signing secret and reject unsigned or invalid requests.
4.3 Secure your endpoint. You are responsible for the security and availability of your endpoint, which must use HTTPS. We may disable a webhook that repeatedly fails or appears insecure.
5. What You Build Is Your Responsibility
5.1 Sole responsibility. Everything you build, connect or operate using the Developer Services is your sole responsibility, including automations, CRM integrations and workflows, dialers and power dialers, SMS and email platforms, marketing-automation tools, AI agents and voice agents, and all of their content, cadence, targeting, timing and consent, opt-out and DNC logic.
5.2 Automated contact. Any automation, dialer, SMS/MMS or email tool, robocall or prerecorded/AI voice system, AI agent or CRM workflow you build, feed or operate with the Developer Services or data received through them is your sole responsibility and must comply with Section 3 of the DLA, including that any contact is made only in strict compliance with all applicable laws, with any required prior express (written) consent, after DNC scrubbing, and with opt-outs and revocations honored. Unlawful automated contact (including Unlawful Outreach as defined in the DLA) is prohibited and is grounds for immediate suspension or termination without notice or refund. Any contact you or anything you build makes is entirely at your own risk. We do not condone, recommend or encourage automated calling, texting, emailing or AI-voice contact with homeowners or other consumers identified in our data, and any automated contact with realtors, agents or brokers is subject to DLA Section 3 in full. Any outreach services we provide to you under a separate agreement are governed by that agreement and do not change the DLA or these API Terms. Delivery of a record by API, MCP or webhook — including any phone, email or DNC field — is not consent to contact that person, not a compliance check, and not a recommendation to contact them.
5.3 DLA applies in full. The DLA's terms on informational use, lawful contact only, prohibited uses (including Unlawful Outreach), suppressed and protected records, the FCRA certification, liquidated damages, no consent, best-effort DNC/TCPA flags, outreach at your own risk, compliance responsibility, record-keeping and audit, indemnification (including that we will not defend you), suspension and termination, and liability apply in full to all data received through the Developer Services and to everything you build with it.
5.4 AI agents. If you give an AI agent or third-party tool access to the Developer Services, you are responsible for its actions and outputs as if they were your own, and you must configure it so it cannot redistribute Licensed Data, ignore suppression notices or initiate Outreach that does not comply with Section 3 of the DLA.
6. No Redistribution or Third-Party Display
You may not use the Developer Services to redistribute, resell, syndicate, display or make Licensed Data available to any third party, including in your own customer-facing application, portal, marketplace or feed, or to power a product used by others, unless we have expressly agreed otherwise in a signed order form.
7. Security and Breach Notice
7.1 You will maintain reasonable security for all systems that receive, store or process Licensed Data or Credentials, including access controls, encryption in transit, and logging.
7.2 You will notify us at support@movingletters.ai within twenty-four (24) hours of discovering any actual or reasonably suspected compromise of a Credential, your endpoint, or any system holding Licensed Data, and cooperate with our investigation.
8. Changes, Versioning and Deprecation
8.1 We may change, version or deprecate endpoints, fields, event types, MCP tools and limits. We will use reasonable efforts to give advance notice of breaking changes or deprecations by email, in the dashboard or in our API documentation, except where a change is needed for security, legal compliance or to protect our data sources.
8.2 No SLA. The Developer Services are provided "as is" and "as available" without any uptime, latency or support commitment, unless a service-level agreement is set out in a signed order form.
9. Suspension
We may immediately suspend or revoke any Credential, webhook or your Developer Services access, with or without notice and in our sole discretion, on any suspected misuse or security risk, any suspected breach of these API Terms or the DLA, or any single consumer complaint or regulator or attorney inquiry, and may terminate without cure on a repeat, as set out in Section 10 of the DLA. No refund is owed.
10. Updates to these API Terms
10.1 We may update these API Terms. We will post the new version with its version number and effective date and notify you by email and in the dashboard. An update takes effect on the stated effective date, which will be at least thirty (30) days after notice or the start of your next billing cycle, whichever comes first, unless required sooner by law or to address misuse. Material changes require click re-acceptance at your next login or before creating new Credentials.
10.2 Existing keys, credentials and webhooks continue to operate under the version in force when they were created until an updated version takes effect; your continued use of any existing Credential or webhook after the effective date of an updated version constitutes acceptance of that version.
10.3 The DLA's terms on data you already hold, survival of prior obligations, confirmation of prior compliance and annual reconfirmation (DLA Sections 16.6–16.10) also apply to these API Terms. Annual reconfirmation in the dashboard does not by itself interrupt API, MCP or webhook delivery unless we tell you otherwise.
10.4 If you do not agree to an updated version, revoke your Credentials, delete your webhooks and stop using the Developer Services.
11. General
These API Terms are an addendum to the DLA and are governed by its general terms, including governing law, dispute resolution, survival and order of precedence. Sections 2.2, 5, 6, 7 and 9 survive termination.
Questions: support@movingletters.ai
Previous versions
Earlier versions are available on request.
Copies of prior versions are available on request from support@movingletters.ai.