VALUEWORKSInsights to Results
Sign in
Help center
Administrator rights required

AI and API settings

Find and read the AI and integration configuration a developer or vendor will eventually ask about.

Three separate pages, three separate kinds of access — mixing them up is the fastest way to hand someone the wrong key.

ChatGPT API Settings explains its own scope directly: ValueWorks uses ChatGPT to, for example, recommend OKR formulations or suggest root causes for underperforming KPIs — and states plainly what is and isn't shared: "no numeric (and thus confidential) company data will be shared. What will be shared, however, are Objective or Key Result names, or rough indications of KPI performance such as 'perform better than previous month.'" Using it at all requires accepting a data processing agreement — two checkboxes (agreeing to the terms; confirming the authority to agree on the company's behalf), a Download blank data processing agreement button, and a Change log recording every time the agreement was generated or accepted, by whom, and when.

API Settings (plain) is a different thing: "Create keys that expose selected KPIs through the ValueWorks API. Each key is shown once at creation." Two tabs, Keys and Log. The Keys table: Name, Key (masked after creation), Access (how many KPIs that key can reach), Expires, Last used, Created by, Created, Actions. A real key in this tenant was scoped to exactly 35 KPIs — access is deliberately narrow, not all-or-nothing.

MCP Server is the third page, and the one that connects ValueWorks to an AI client like Claude Desktop. Two tabs: OAuth — sign in with your ValueWorks account directly in the client, "so there is no API key to create or store" — and API Key, the alternative for clients that need one. The OAuth tab gives a ready-made server URL and three steps: add that URL as an MCP server in your client, sign in when prompted, and the connection stays active until removed from the client side.

The ChatGPT API Settings page, explaining what ValueWorks shares with ChatGPT (Objective and Key Result names, rough KPI performance trends — never numeric confidential data), above a Download blank data processing agreement button, an Edit company info button, two checked agreement checkboxes, a Generate new version button, a Tokens Usage bar at 0%, and a Change log table of who generated or accepted the agreement and when.
The API Settings page's Keys tab, with Keys and Log tabs, an API Reference button and a + Create API key button, above a table listing one real key —
The MCP Server page's OAuth tab, explaining that signing in with your ValueWorks account means there's no API key to create or store, above a Recommended MCP Server URL field with a copy button and three numbered steps: add the URL as an MCP server in your client (Claude Desktop, Langdock, etc.), sign in with your ValueWorks account when the client prompts you, and the connection stays active until you remove it from the client.
The MCP Server page's API Key tab, explaining that API keys let external MCP clients connect with read-only, superuser-level access, above an MCP Endpoint URL field with a copy button, a Key Name input and Create API Key button, and a table listing one existing key — Lovable, masked after vw_339daec, created Mar 9, 2026, tagged Read-only scope · Administrator-level access.
The API Settings page's Log tab, listing a history of key actions — Action, Token name, Timestamp, Executed by, Details — including Created and Deleted entries for keys named test, test1 and API test key, and one Created entry for API for Board Reporting scoped to 35 KPI(s).
The New API key creation screen, with Key Name and Valid For (90 days) fields, an All categories filter and Search KPI box above a 0 / 1215 KPI(s) counter, a table of individual KPIs each with its own KPI and List checkboxes, Category, KPI name and ID, and a summary bar at the bottom (Unnamed key, 0 KPI(s), 0 List view, Expires 90 days) with a disabled Create API key button until something is named and selected.

Takeaways

  • ChatGPT API Settings governs an AI feature inside ValueWorks — names and rough trend language may be shared, never numeric confidential data — gated by a data processing agreement.

  • API Settings creates keys that expose selected KPIs to the outside world — each key scoped to a specific number of KPIs, not full access by default.

  • MCP Server connects an AI client (like Claude Desktop) to ValueWorks — OAuth needs no key at all; API Key is the fallback.

Surfaces covered

  • ChatGPT API Settings
  • AI usage & limits
  • API Settings
  • MCP Server (OAuth and API Key)

Also taught in the Academy

Module 13 · Settings and KPI Management

Take it as lesson 13.6 in Business Analyst & FP&A