# API & CLI: Your GEO data, in your own code. > CiteAPI is a REST API on the same data as the Citeme platform: pull every audit of a project into your own reporting and export your reports at any time. [HTML version](https://www.citeme.io/features/api) --- CiteAPI is a REST API on the same data as the platform. Pull every audit of a project into your own reporting, build a dashboard, a script or a product feature, and keep your keys encrypted and revocable. ## Key numbers - **10** AI engines behind the data - **AES-256** GCM-encrypted keys - **4** last characters of a key shown - **1** citeme login for CLI and MCP ## What is CiteAPI? CiteAPI is Citeme's REST API. You write code against it, you handle auth, pagination and shapes yourself, and you get exactly what you asked for. It serves the same data as the MCP server to a different consumer: your code rather than a model. Use it when you are building something: a dashboard, a script, a product feature. ## Same data, your own code. ### Every audit, one GET A GET on the audits of a project returns the full list, which is how you pull scores into your own reporting. ### Full audit records Each audit comes with its score, status, duration in milliseconds, creation timestamp and technical details, including the model that answered and the region simulated. ### Incoming webhooks An incoming webhook trigger generates a URL any external system can call. The request body becomes the trigger payload, reusable by every node downstream. ### One login, CLI and MCP The MCP server reads the same credentials as the Citeme CLI, so on Claude Desktop's local setup or Claude Code a single citeme login covers both. ### Exportable reports Exportable reports are included in the plan, with a ready-made PDF report template. Nothing is deleted if you cancel. ### Encrypted, revocable keys Keys are encrypted with AES-256-GCM, only their last four characters are shown, and revocation is immediate. Leaked cm_live_ keys on public GitHub are revoked outright. ## Pull, sign in, trigger, export. ### Pull audits into reporting A GET on the audits of a project returns the full list: score, status, duration in milliseconds, creation timestamp and technical details. Because the displayed score blends runs, read the series rather than one point. ### One login for CLI and MCP ChatGPT, Cursor and n8n reach the MCP server with a Citeme CLI key from your account. On Claude Desktop's local setup or Claude Code, the server reads the CLI credentials, so a single citeme login covers both. ### Trigger Nova from outside The incoming webhook trigger generates a URL any external system can call. The request body becomes the trigger payload, so your own stack can hand Nova a task. ### Export your reports Exportable reports are included in the plan, with a ready-made PDF report template. Cancel and the account turns read-only at the end of the paid period: nothing is deleted, export whenever you want. ## Three steps. No setup project. 1. **Sign in once** Run citeme login, or use a Citeme CLI key from your account for MCP clients. 2. **Pull your audits** A GET on the audits of a project returns the full list. 3. **Use your own tools** Chart scores in your own reporting, or export reports from Citeme. ## FAQ ### Should I use the API or the MCP server? Same data, different consumer. If you are integrating Citeme into software, use the API: you write the requests and handle auth, pagination and shapes. If you want to ask questions about your GEO in the assistant you already have open, use the MCP server: it describes its own tools and you never write a request. ### Can I pull audit scores into my own reporting? Yes. A GET on the audits of a project returns the full list, each audit stored with its score, status, duration in milliseconds, creation timestamp and technical details, including which model answered and which region was simulated. Because the displayed score blends the current run with previous ones, a genuine improvement shows up over two or three audits. ### Can I trigger a new audit through the API? Triggering a fresh audit through the API is restricted, and every audit launched consumes monthly quota credits. Pulling the audits a project already has is how you feed your own reporting. ### How does the Citeme CLI relate to the MCP server? ChatGPT, Cursor, n8n and other MCP clients authenticate to the remote MCP server with a Citeme CLI key from your account. For the local configuration of Claude Desktop, or for Claude Code, the server reads the same credentials as the Citeme CLI, so a single citeme login covers both. In Claude itself, the OAuth connector needs no key. ### How are keys protected? Keys are encrypted at rest with AES-256-GCM, with the encryption keys in a separate KMS, and the dashboard shows only the last four characters. Revocation from settings is immediate. Citeme scans public GitHub repositories continuously and revokes any leaked key in its own cm_live_ format, notifying the owner by email. An Editor can launch audits that use keys but never see, modify or export them. ### Can I export my reports? Yes. Exportable reports are included in the plan, with a ready-made PDF report template. If you cancel, your account stays available until the end of the period you paid for, then turns read-only. Nothing is deleted: you can export your reports and content whenever you want. ## Related pages - [MCP Server](https://www.citeme.io/features/mcp): Your data in ChatGPT, Claude & Cursor - [Integrations](https://www.citeme.io/features/integrations): Ship fixes through your own stack - [Nova, AI agent](https://www.citeme.io/features/ai-agents): Finds the gap, drafts the fix - [GEO Audit](https://www.citeme.io/features/geo-audit): What AI says about you