generated: '2026-09-13' method: searched source: - https://developer.vismaonline.com/docs/spiris-mcp-server - https://docs.vismasoftware.no/vismanetapi/introduction/getting-started-with-visma-net-api/ - https://oauth.developers.visma.com/service-registry/ plan_count: 1 note: 'Visma publishes NO API pricing. API access is an attribute of a product subscription and of a partner/integrator relationship, not a separately priced product: an integrator registers an application in the Visma Developer Portal, the application is approved by Visma, and the calls are then billed (or not) through the customer''s own Visma product licence. There is no public per-call price, no free tier published as a tier, and no self-serve checkout. The one priced statement Visma does publish about an API surface is the Spiris MCP beta, recorded below. developer.visma.com/pricing returns HTTP 200 but is the Angular SPA shell, not a pricing page.' plans: - name: Spiris MCP - Beta price: 0 currency: SEK billing_period: month included: Access to the Spiris MCP server for a company with a Spiris subscription, enabled per user. overage: null limits: Governed by the eAccounting API limit of 600 requests per minute per client and endpoint. source: https://developer.vismaonline.com/docs/spiris-mcp-server note: Visma states a monthly fee will be introduced before general release, communicated in advance. access_model: visma_net_erp: Register an application in the Visma Developer Portal; Visma approves it before production credentials are issued. Requires a Visma.net ERP customer tenant to call against. eaccounting: Spiris Partner Programme registration issues the client_id and redirect_uri; a sandbox client is provisioned for development. business_nxt: Visma Developer Portal application plus a per-company AI permission toggle for the MCP surface. evidence: - url: https://developer.visma.com/pricing status: 200 note: SPA shell, identical bytes to every other path on that host — not a pricing page. - url: https://www.visma.com/pricing status: 404