ifrCoworker — Terms of Service
Effective Date: 29 March 2026 · Service operated by SPOCONT Ltd.
1. Service Description
ifrCoworker provides IFRS/IAS financial reporting calculations, journal entries, disclosures, and XBRL tagging via API and MCP endpoints. The service covers 27 standards with over 200 accounting transaction types.
2. Design Philosophy — MCP First
ifrCoworker is designed as an MCP-first service. The primary integration path is the Model Context Protocol (MCP), which allows AI agents to discover endpoints, inspect schemas at runtime, and adapt to changes without client-side code updates. Versioning and backward compatibility of individual endpoints are explicitly secondary concerns — MCP agents query the /schema endpoint before each session and always operate against the current field definitions. Individual endpoints carry no version suffix; the only version number is that of the OpenAPI specification document itself.
We actively rely on the flexibility of MCP agents as the foundation for responsible, prudential but definitive evolution of the service: field names, enums, and calculation rules may change as IFRS/IAS standards are updated or corrected, and we trust that well-implemented MCP agents will adapt gracefully by re-reading the schema. The service follows an early adoption principle — new and amended standards are adopted as soon as they become effective, without waiting for wide market uptake.
Bug fixes are deployed immediately as soon as they are identified and verified, without a release cycle. Users are encouraged to re-query the schema after any service update notice.
3. Request-Based Billing
The service is billed on a per-request basis. Each API or MCP call that triggers a calculate or validate operation counts as one request. Where a calculation involves multiple standards (cross-standard redirects such as IAS 12 deferred tax, IAS 21 foreign exchange, or IAS 23 borrowing costs triggered within a single request), each standard invoked counts as a separate request against your quota. Schema queries are free and unlimited.
4. Quota and Expiry
Purchased request quotas are valid for the period specified at purchase. Unused requests may expire 90 days after the purchase date. No refunds are provided for expired, unused requests. You can check your remaining quota at any time via the /api/ifrs/access/status endpoint.
5. Accuracy and Liability
The service provides deterministic IFRS/IAS calculations based on the standards as published by the IASB. It is a calculation and reporting tool — it does not constitute professional accounting, audit, legal, or tax advice, and does not replace the professional judgement of a qualified accountant or auditor. Outputs are generated programmatically from the inputs provided; their accuracy depends entirely on the completeness and correctness of those inputs. All outputs — including journal entries, measurements, disclosures, XBRL tags, and consolidation working papers — must be independently reviewed by a qualified accountant or auditor before use in financial reporting, regulatory filings, or any decision-making context. Users are solely responsible for verifying results and for the accuracy of any financial statements in which those results are used. SPOCONT Ltd. expressly excludes all liability for any loss, damage, or liability arising from incorrect or incomplete inputs, reliance on any output without independent review, or any failure to apply professional judgement. To the maximum extent permitted by applicable law, any remaining liability of SPOCONT Ltd. that cannot be excluded shall in no event exceed the total service fees paid by the user to SPOCONT Ltd. in the six (6) months immediately preceding the event giving rise to the claim.
6. XBRL Taxonomy
Journal entries are enriched with ESEF XBRL tags from the IFRSAT-2025 taxonomy (xbrl.ifrs.org/taxonomy/2025-03-27). Tags are provided for convenience and may not cover all entity-specific accounts. Users should validate XBRL tagging against their own filing requirements.
7. Data and Privacy
We store your email address and a record of API usage (standard, method, timestamp) for quota enforcement and service improvement. Calculation inputs and outputs are not stored — they are processed in memory and discarded. We do not share your data with third parties.
8. Intellectual Property and Prohibited Use
The calculation logic, chain orchestration, XBRL mapping, field definitions, and all software underlying the ifrCoworker service are the exclusive intellectual property of SPOCONT Ltd. and are protected by copyright and trade secret law. Your API token grants you a limited, non-exclusive, non-transferable licence to access the service for integration purposes only. The following are expressly prohibited:
— Reverse engineering: deriving, reconstructing, or inferring the calculation logic, algorithms, or business rules of the service from API inputs, outputs, schema definitions, or error messages;
— Reimplementation: building a competing product or service that replicates the functionality of ifrCoworker based on knowledge gained through use of the API;
— Redistribution: sharing, reselling, sublicensing, or publishing API responses — including calculation results, journal entries, disclosures, or XBRL tags — to third parties without prior written consent from SPOCONT Ltd.;
— Systematic extraction: automated or scripted bulk querying of schema, validate, or calculate endpoints for the purpose of mapping service behaviour rather than legitimate integration use.
Each API response includes a _license block identifying the token holder. This watermark is logged and may be used as evidence in the event of misuse. Violation of this section constitutes a material breach of these terms and may result in immediate termination, legal action, or both.
9. Termination
We reserve the right to suspend or terminate access for abuse, excessive load, or violation of these terms, without prior notice. You may stop using the service at any time.
By purchasing a token or using the API, you agree to these terms. · Contact: hello@spocont.com