Your account and API access¶
Sign in with email and password, Google or your Orvel account. Your workspace shows your allowance and remaining operations. Purchases made there are linked to your account; signing in again does not reset your trial or purchased credits.
Connect with your account¶
Add https://facturx.orvel.dev/mcp/account to an OAuth-capable MCP client, select Authenticate, sign in and approve the connection. An existing Orvel session can skip the sign-in step. Your connection uses the allowance selected in your workspace. See MCP setup for client-specific steps.
REST API and existing keys¶
Use the workspace's API-key reveal button when you need a bearer key for REST. You may be asked to sign in again before revealing it. Keep the key private.
Existing API keys still work. The section below also supports older checkout return links, whose access is time-limited; it is not needed for the account sign-in flow.
Use it¶
REST: https://facturx.orvel.dev/v1/... — MCP: https://facturx.orvel.dev/mcp. Examples: Quickstart, MCP.
Check usage: GET /v1/usage with the same header.
Manage billing¶
For a monthly subscription, open billing from your workspace to manage the plan, cancellation, invoices and payment method. If you have several saved allowances, select the subscription first. You can also use an existing subscription key with the form below.
Prepaid credits have no subscription or automatic recharge. Each EUR 10 purchase adds 100 operations to the same balance, without expiry. A monthly subscription has a separate allowance; switching plans does not discard unused prepaid credits. Static API keys remain bound to their original allowance.
Existing EUR 3 evaluation packs keep their 25 operations and 30-day expiry. New evaluation purchases are retired. For receipts or billing help, contact antoine.le.borgne@orvel.dev.
Clients using a static API key¶
If an older checkout link displays a key above, its copy buttons provide configurations for Cursor (.cursor/mcp.json), VS Code (.vscode/mcp.json) or Claude Desktop (its claude_desktop_config.json, with Node.js installed). Keep these key-containing files private. Reconnect your client after saving. For account sign-in, use /mcp/account as described above.
Click Check key and MCP connection to verify your allowance and tool discovery without spending a document operation. Then ask your assistant to call get_invoice_example and generate that example as cii-xml. This first document call uses one operation. See MCP setup for Claude Code and other clients.