API & Developer Terms

These Terms provide the written approval required under the Platform Terms for a Developer to build an approved Customer Application, serve direct business End Clients, and operate approved child organizations. They do not authorize full white-label replacement of the ALEBEX-hosted interface, multi-level resale, or sub-resellers unless a separate enterprise agreement expressly permits it.

These ALEBEX AI API Developer, Embedded Application and Platform Partner Terms (the “Developer Terms”) supplement the ALEBEX AI Online Platform Terms of Service between ALEBEX AI Corp. (“ALEBEX”) and the person or entity identified in the Developer Account (“Developer”). The Platform Terms, AUP, Communications Policy, DPA, Country Requirements, applicable pricing or Order Form, and these Developer Terms form the “Developer Agreement.”

By selecting a developer, API, embedded, or platform-partner account and affirmatively accepting the applicable bundle, the accepting person represents authority to bind Developer. If no separate legal entity is identified, the accepting person is Developer and assumes the obligations personally.

These Developer Terms constitute ALEBEX’s written approval, for purposes of the Platform Terms, for the limited embedded and downstream model expressly authorized here and enabled in Developer’s Account. Any use outside that model remains prohibited unless ALEBEX gives additional written or in-product approval.

“Developer Application” means Developer’s independently developed website, software, CRM, workflow, platform, application, or service that integrates the ALEBEX API or other enabled Services. “Downstream User” means an End Client, Authorized Organization, administrator, operator, customer user, or other person accessing or benefiting from a Developer Application.

“End Client” means a business or organization to which Developer provides or enables an ALEBEX-powered service. “Authorized Organization” means an End Client created as a child organization or sub-organization under an approved Platform Partner Account and bound to the ALEBEX Authorized Organization and Platform Use Acknowledgment or equivalent approved terms.

A “Standard Developer” builds an internal or customer-facing application and may serve direct End Clients through Developer’s own interface. A “Platform Partner” is an approved Developer that may create and co-manage Authorized Organizations using ALEBEX partner and child-organization tools and may receive account-specific wholesale or discounted rates under an Order Form. Neither status gives full white-label rights.

Capitalized terms not defined here have the meanings in the Platform Terms, DPA, AUP, Communications Policy, or Country Requirements.

Subject to the Developer Agreement and payment, ALEBEX grants Developer a limited, non-exclusive, revocable, non-transferable, and non-sublicensable right during the Term to access the enabled APIs, SDKs, developer tools, portal, documentation, webhooks, and related Services solely to build, test, operate, and support the approved Developer Application and direct End Clients.

Developer may make approved ALEBEX-powered functionality available to direct End Clients as part of Developer’s own materially integrated application, product, workflow, or service. Developer may not sell the ALEBEX API, raw model access, credentials, telephone resources, or unmodified ALEBEX functionality as a standalone service; expose credentials to an End Client; permit an End Client to extract or directly call undocumented ALEBEX interfaces; or represent that an End Client has a direct ALEBEX account unless ALEBEX separately agrees.

Developer may serve its own direct business End Clients without individual ALEBEX pre-approval where the End Client falls within enabled countries and standard uses, Developer completes required organization information and flow-down acceptance, and no automated or manual risk trigger applies. Developer may not appoint a sub-reseller, allow an End Client to distribute to another tier, or create a marketplace of resellers without ALEBEX’s prior written approval.

Developer is responsible for all use through its credentials, Developer Application, partner portal, child organizations, End Clients, Downstream Users, integrations, numbers, and configurations. Developer may not use multiple Accounts or entities to evade pricing, limits, review, or restricted-use controls.

ALEBEX may provide testing minutes and non-production or limited production access for integration and quality testing. Testing minutes may be used only with Customer-controlled test numbers or persons who knowingly agreed to participate, using synthetic or approved data. They may not be used for live commercial campaigns or Restricted Data unless ALEBEX expressly enables that use.

Production outbound functionality remains locked until Developer secures an approved payment source, accepts the applicable legal bundle, completes the communications attestation, verifies required caller or sender identity information, identifies intended countries and communication categories, and satisfies any automated or risk-triggered controls. ALEBEX may enable standard outbound access automatically after these steps.

Developer must use documented authentication methods, rate and concurrency limits, approved environments, webhooks, portal controls, and technical specifications. Developer must not scrape or call undocumented endpoints, interfere with logs, bypass billing or safety controls, modify generated identifiers, obscure the actual sponsor, or use credentials outside approved systems.

Developer must design secure retry, error handling, idempotency, rate limiting, logging, fallback, human escalation, and service-unavailability behavior. Developer must not make the availability of an emergency, safety-critical, regulated, or essential service depend solely on ALEBEX.

Developer contracts with and manages its End Clients and remains responsible for them. ALEBEX does not contract with an End Client unless the End Client separately accepts ALEBEX terms or ALEBEX expressly agrees. Developer bears downstream pricing, billing, refunds, chargebacks, bad debt, support, and customer-relationship obligations.

Before enabling an End Client, Developer must bind it to enforceable written or electronic terms that authorize the intended AI voice, communications, data, recording, transcription, analysis, routing, CRM, and related processing and that are at least as protective of ALEBEX as the applicable AUP, Communications Policy, Country Requirements, DPA flow-down, intellectual-property restrictions, security requirements, suspension rights, disclaimers, and limits on ALEBEX obligations.

Where Developer uses ALEBEX child-organization tools or an ALEBEX-hosted interface, each Authorized Organization must accept the then-current ALEBEX Authorized Organization and Platform Use Acknowledgment before production access. Where Developer uses only its own interface, Developer may use equivalent downstream terms approved in substance by ALEBEX. Developer must retain the accepted version, identity and authority of the accepting person, date, time, organization, and acceptance evidence.

ALEBEX is an intended third-party beneficiary of downstream provisions protecting ALEBEX IP, Confidential Information, data-processing authority, platform security, acceptable use, suspension, audit, disclaimers, and limits on ALEBEX obligations, or Developer must provide an equivalent direct-enforcement mechanism. Developer remains responsible if its downstream terms are incomplete or unenforceable.

Developer must promptly suspend a Downstream User, End Client, Authorized Organization, campaign, number, voice, feature, or credential when directed by ALEBEX. ALEBEX may act directly where reasonably necessary to protect the Services, and Developer must preserve End-Client and acceptance records.

An Account enabled as a Platform Partner may create and co-manage direct business Authorized Organizations within the countries, industries, services, and rate plans enabled in the Account or Order Form. ALEBEX does not routinely pre-approve each Authorized Organization. Developer must collect accurate organization name, responsible contact, business description, country, industry, enabled channels, general communication purpose, and whether a Restricted Use applies.

Developer must perform risk-based verification appropriate to the service, including verifying business identity, administrator, payment allocation, campaign sponsor, website or business presence, and other information ALEBEX requires. Developer must not create anonymous, pseudonymous, disposable, shell, concealed, or misleading organizations or use Developer’s identity or number to hide the actual sponsor.

Developer may onboard its own direct customers. Developer may not onboard another partner, reseller, agency chain, marketplace operator, or party that will further distribute the Services without ALEBEX’s prior approval and, where required, an enterprise agreement.

Developer must update organization information when ownership, use, country, industry, data category, volume, caller identity, custom voice, payment risk, or complaint pattern materially changes. Standard changes within an enabled category do not require a new legal schedule. A Restricted Use or risk trigger may require evidence, limits, or review.

Developer is responsible for the design and legal operation of communications through the Developer Application, including recipient eligibility, consent or other lawful basis, scripts and prompts, contact sources, caller and sender identity, calling hours, recording and transcription, AI or automation disclosure where required, opt-outs, suppression, do-not-call and anti-spam controls, and human escalation.

Developer must implement an outbound communications gate that prevents production outbound access until the applicable organization has completed the required ALEBEX legal acceptance or flow-down, payment-source requirement, communications attestation, caller or sender identity step, country selection, and use-category declaration. Developer must not represent that completing the gate constitutes legal clearance.

Ordinary sales outreach, lead follow-up, appointment setting, customer service, reactivation, surveys, notifications, business development, and other standard communications do not require a separate Schedule F or campaign-by-campaign ALEBEX approval where the required gates are complete and no Restricted Use or risk trigger applies.

Purchased or third-party lists may be subject to additional review. Scraped lists, stolen data, lists lacking lawful rights, or data obtained through deception are prohibited. Developer must retain the evidence supporting its lawful contact position and must honor opt-outs and suppression immediately.

Developer must keep communications compliance records for at least five years and ordinary actor, configuration, and acceptance logs for at least twenty-four months. Records must identify the actor, time, organization, prior and new setting where applicable, campaign or workflow affected, terms version, and relevant approval or attestation. Developer will provide reasonable evidence promptly after an ALEBEX request.

Custom voice activation requires an electronic certification that the organization has all rights, permissions, and consents necessary to upload, create, and use the voice and to authorize ALEBEX and its providers to process it. Developer must not use a voice for impersonation, deception, false authority, authentication circumvention, or fraud. ALEBEX may disable a voice immediately after a complaint or rights dispute.

Developer must maintain a secure development lifecycle and reasonable administrative, technical, and physical safeguards, including code review, dependency management, access control, available multi-factor authentication, secret management, encryption in transit, tenant separation, secure logging, vulnerability remediation, backup and recovery, and personnel confidentiality.

Developer must not place API keys, tokens, certificates, private keys, webhook secrets, or other credentials in client-side code, public repositories, shared documents, customer tickets, or other insecure locations. Developer must rotate credentials promptly after suspected exposure and must maintain separate credentials and permissions where ALEBEX supports them.

Developer must notify ALEBEX immediately, and no later than twenty-four hours after discovery, of a Security Incident, credential exposure, fraud, unlawful calling, carrier block, voice-rights complaint, widespread disclosure failure, regulator inquiry, or material customer harm. Developer must contain the event, preserve evidence, cooperate, and provide timely updates.

ALEBEX may require a security questionnaire, architecture or data-flow diagram, penetration-test summary, independent report, remediation plan, enhanced controls, or security review before production, after a material change, or after an incident. Developer must not make public claims regarding ALEBEX security certifications or architecture without written approval.

Developer provides first-line support for the Developer Application and End Clients, including onboarding, configuration, billing, user training, scripts, prompts, data quality, consent and disclosure settings, and ordinary troubleshooting. ALEBEX supports Developer, not End Clients, unless an Order Form states otherwise.

Developer must test material changes, maintain appropriate human oversight, and provide fallback and escalation for inaccurate, unsafe, sensitive, regulated, or unsupported interactions. Developer is responsible for the quality and accuracy of Developer-controlled prompts, knowledge, claims, business rules, integrations, and workflows.

Developer must not promise an ALEBEX feature, uptime, service credit, support response, data location, certification, roadmap, language, model behavior, accuracy, legal compliance result, indemnity, or remedy beyond the Developer Agreement. Developer bears responsibility for any additional commitment it makes.

Developer may brand its independently developed Developer Application and customer service. If Developer or an Authorized Organization logs into or uses an ALEBEX-hosted interface, ALEBEX branding and required legal notices remain visible unless an Enterprise Order Form expressly permits replacement.

Developer may use a separate domain for Developer’s own application or workflow. Developer may not remove or replace ALEBEX logos from the ALEBEX-hosted application, present an ALEBEX-hosted interface under a partner-controlled domain as Developer’s complete proprietary platform, or offer a full logo/domain replacement without an Enterprise White-Label MSA and Order Form.

Developer must not state or imply that it owns, developed, independently operates, audits, certifies, or guarantees the ALEBEX backend, models, voices, infrastructure, security, or compliance. Developer may not use ALEBEX names, marks, screenshots, non-public documentation, customer names, case studies, or benchmarks without written approval.

Developer is responsible for all marketing claims concerning accuracy, latency, uptime, languages, voice quality, security, privacy, compliance, conversion, results, and roadmap. Claims that identify or depend on ALEBEX must be accurate, substantiated, and revised or removed on ALEBEX request.

Developer retains its independently developed application code, interface, brand, workflows, and materials. ALEBEX retains ALEBEX IP. Integration, configuration, testing, support, or feedback does not transfer ownership or create joint ownership unless a signed development agreement expressly states otherwise.

Developer must identify and document the applicable controller, processor, business, service-provider, organization, contractor, and subprocessor roles for each End Client and must have authority to appoint ALEBEX and its providers. Developer must not configure processing in conflict with the DPA or End-Client instructions.

Developer must not use ALEBEX Confidential Information, non-public prompts, system prompts, architecture, orchestration, logs, traces, support materials, test results, training materials, or Output to train, fine-tune, extract, benchmark, validate, or improve a competing AI voice or agentic platform, except ordinary quality assurance and tuning of the authorized ALEBEX integration.

The preceding restriction does not prevent independent development or use of competing technology without ALEBEX Confidential Information or ALEBEX IP. Developer must not introduce code, data, models, licences, or materials into an ALEBEX integration in a way that imposes disclosure, source-availability, attribution, licensing, security, or other obligations on ALEBEX without prior approval.

Unless an Order Form states otherwise, Developer pays the published or account-specific subscription and usage rates displayed in the Account. Developer or API Accounts may have usage-only pricing. A Platform Partner may receive organization-specific rates, platform discounts, or wholesale pricing in an electronic Order Form.

Developer’s payment obligation to ALEBEX is independent of whether Developer collects from an End Client. Developer bears downstream credit, refund, dispute, chargeback, tax, fraud, and bad-debt risk. Developer may set its End-Client prices but may not represent that ALEBEX is the seller or merchant of record for Developer’s End-Client service unless ALEBEX separately agrees.

Developer must maintain an approved payment source and comply with credit, deposit, prepayment, usage-cap, concurrency, and billing controls. International carrier and other pass-through charges may apply. The refund and billing provisions of the Platform Terms apply.

ALEBEX may monitor traffic, volume, destinations, complaints, opt-outs, short calls, caller identity, security events, payment patterns, account creation, configuration changes, and other operational information. ALEBEX may request evidence, throttle, restrict countries or features, lower limits, require reverification, suspend a Downstream User or organization, rotate credentials, or terminate access where risk is reasonably identified.

ALEBEX may require Developer to migrate to an enterprise agreement before continuing or expanding use where Developer requests full white-label branding, custom domains for the ALEBEX-hosted interface, sub-resellers, dedicated infrastructure, custom service levels, custom security or data terms, substantial wholesale commitments, regulated uses, Restricted Data, new countries, unusual volume, or negotiated liability or indemnity terms.

Where risk permits, ALEBEX will use commercially reasonable efforts to provide a reasonable migration period. ALEBEX may restrict new organizations, new countries, increased volume, or new features until the required agreement is signed. Existing payment, compliance, data, and intellectual-property obligations continue during migration.

Developer’s indemnity under the Platform Terms includes claims arising from End Clients, Authorized Organizations, Downstream Users, Developer Applications, flow-down failure, KYC or verification failure, unlawful communications, contact lists, unauthorized voices, data or security incidents within Developer’s control, Developer commitments, downstream billing, and Developer’s failure to suspend or cooperate.

The exclusions and limitation of liability in the Platform Terms apply to these Developer Terms. No End Client or Downstream User receives a greater ALEBEX remedy or liability commitment than Developer receives. Developer is responsible for any additional warranty, indemnity, service level, credit, or remedy it offers.

These Developer Terms control over the Platform Terms for embedded applications, downstream distribution, Platform Partner tools, and End Clients. The DPA controls processing topics, and the AUP, Communications Policy, and Country Requirements control use and communications topics. An Order Form controls only its stated commercial and technical fields.

These Developer Terms remain effective while Developer has developer or partner access or a Developer Application uses the Services. Termination of the Platform Terms terminates these Developer Terms. ALEBEX may terminate developer or partner rights without terminating unrelated direct-use Services where reasonably practicable.

ALEBEX may update these Developer Terms under the change provisions of the Platform Terms. ALEBEX may require reacceptance after a material change or before enabling a new category of downstream use.