Common use of API Integrations Clause in Contracts

API Integrations. In exchange for a *** paid by AT&T to Motricity, Motricity shall support 10 standard API integrations over a twelve (12) month span, which includes current projects Media Net 4 and Media Mall. Notwithstanding the foregoing, Motricity shall waive the *** fee for each month in which Total Gross Revenue through the client API exceeds *** Motricity shall invoice any such fees monthly in arrears. Although payment is recurring and will be made monthly starting when this amendment is signed, if an API integration is delayed due to fault of Motricity, the monthly fee would be reduced proportionally (example - if Motricity can support 3 integrations concurrently and one is delayed due to Motricity fault, the monthly fee would be reduced by one third for that month, and subsequent months, until corrected). A project plan will be mutually agreed upon by Motricity, the client application provider, and AT&T at the start of each new API integration project. Motricity will be subject to NPCs upon failure to meet the committed number of standard integrations (10) for 2008. *** It is estimated that a standard API integration would take *** per integration to reach a production ready state and an additional *** per month to support. The impacts by functional area are: • *** Initial Consultation • *** Integration Support • *** Configuration The deliverables for a standard implementation are outlined in the table below: Catalog Motricity will provide access to the current Client catalog Catalog Maintenance Motricity will provide ongoing maintenance to the Client catalog to ensure fresh content Integration Kickoff Motricity will chair a kick-off meeting via conference call for each integration. Integration Support Motricity will provide integration support for each integration via email. In-life Support Motricity will provide in-life technical support for each integration for a period of 2 years past execution of the SOW Upgrade Path Motricity will provide a smooth upgrade path for each integration for a period of 2 years past execution of the SOW Documentation Motricity will provide all relevant API documentation Production Support The production APIs will be monitored 24x7x365 via Motricity NOC personnel The following items are assumptions, dependencies & risks associated with the AT&T Standard Client API Integrations: • As part of a standard integration, support will only cover API specific questions, not application specific questions. • Standard Integration fees apply only to the existing API specifications. Any requested change to the API will be handled via an additional Statement of Work. • API support during the Implementation Phase via email is limited to the hours of 9 am to 5 pm (Eastern Time) Monday through Friday, excluding holidays. 24x7x365 production support will be provided once the client application launches. • The AT&T Dedicated Test Environment will be utilized for pre-production testing. • Only three (3) integrations can concurrently take place through 12 month span. The failure of any of the above assumptions, dependencies, or risks may result in project delays or increased costs for which Motricity is not responsible. For API integration requests that fall outside of this standard integration implementation process, or for which the assumptions, dependencies, and risks prove to be untrue, Motricity provide additional evaluation of the incremental work required and a SOW will be presented to AT&T for the incremental work required.