API income and the Cyprus IP Box

The endpoint does not determine tax treatment

A company can use an API to deliver original software functionality, licensed data, third-party model access or a managed service. Customers may be charged per request in each case. The billing unit does not establish which asset generates the income.

Start with what the customer receives and what the company contributes. Is the company exploiting its own qualifying software, supplying a service supported by software, or passing through another provider’s functionality? The answer may involve more than one component.

The Cyprus regulations include royalties, licensing amounts and embedded income directly related to qualifying IP. That supports examining API-based business models, but it does not create a blanket category in which every API receipt qualifies.

Compare three API business models

These examples organise the questions; they do not replace an assessment of the actual contracts and technology.

Build the revenue and cost bridge

Reconcile recognised API revenue with billing records, usage adjustments, credits and refunds. Then identify the income attributable to the qualifying asset. If the offering includes other components, document the basis for any allocation instead of treating all receipts as qualifying because they share one invoice.

Deduct relevant costs in arriving at net IP income. Production compute, third-party API charges and support can affect the economics, but their treatment must be assessed under the applicable rules. Do not confuse this annual profit calculation with the nexus expenditure schedule.

For example, a third-party model charge may be an operating input to an application. It does not automatically become the company’s qualifying R&D expenditure. Development compute, purchased software and related-party services need their own classifications.

A pricing change can leave the underlying tax question unchanged

Suppose the same proprietary application moves from a monthly subscription to per-request billing. That change alone does not create a new qualifying asset or prove a different nexus fraction. Review whether the rights, functionality and income composition actually changed.

Now suppose the company adds a separately charged human review service to each API response. That is a different commercial development: the offering now includes an additional component whose income and costs may need separate treatment.

The useful distinction is between a billing change and a change in what creates value. Keep the tax analysis tied to the latter while ensuring the accounts reflect the former accurately.

Check provider terms and the company’s own rights

Where external APIs are essential, review the rights and restrictions in the provider agreement. The company’s permission to access a service does not establish ownership of the provider’s software, data or model.

Document the company’s original software contribution and the rights obtained from employees and contractors. If the product contains AI-assisted code or licensed components, preserve the relevant rights analysis rather than assuming the whole stack is exclusively owned.

The API documentation can help explain functionality, but technical documentation alone is not an ownership record. Connect it with contracts, code history and the asset register.

Evidence for a usage-based software business

Create a compact file that links the commercial model, technology and calculation. It should allow a reviewer to follow the income from the customer contract to the relevant asset and then to the net-profit and nexus schedules.

Review the file when major endpoints, providers or pricing bundles change. A conclusion reached for a proprietary software API may not describe a later service that mainly resells access to another platform.

• Customer terms and description of supplied functionality.
• Identified qualifying software and rights chain.
• External provider agreements and material restrictions.
• Billing-to-revenue reconciliation, including credits.
• Supported allocation of mixed income and costs.
• Separate development expenditure history and nexus calculation.
• Explanation of material changes during the year.