Skip to main content
The Permitech integration connects Luna Studio to the rest of the Permitech platform. The Integrations page lets a user save a personal permitech_api record and an administrator save a workspace-scoped record. In the current release, however, dataset import and metric registration do not read either in-app record. Those operations instead read the Permitech API URL and key from deployment settings for the Luna Studio backend.
This is a current-release runtime limitation, not a permanent deployment-only architecture. Saving or successfully testing either a personal or workspace Permitech card does not make those credentials available to dataset import or metric registration.

​
When you need it

The Permitech integration unlocks two platform features:
  • Import from Permitech — pull datasets from your Permitech workspace into Luna Studio. Available when adding a dataset and in Step 2 and Step 3 of the run creation flow.
  • Register metric — publish an eligible fine-tuned metric from Luna Studio into the Permitech metrics store, where it becomes available across evaluation, observability, and guardrails. See Register a metric.
You can use Luna Studio without the Permitech integration — uploads, URL fetches, and local-only flows work fine — but registration and Permitech-sourced data require it.

​
Configure the effective connection in the current release

1

Ask your deployment operator

The operator must configure both the Permitech API URL and API key for the Luna Studio backend. The backend-native environment names are LUNA_PERMITECH_API_URL and LUNA_PERMITECH_API_KEY. The SDK-compatible names PERMITECH_API_URL and PERMITECH_API_KEY are also accepted, allowing the backend and SDK to use the same deployment values.
2

Verify the consuming flows

To verify dataset access, select Import from Permitech while adding a dataset. To verify registration, open an eligible run with the Fine-tuned status and inspect its Register metric action; the run-details preflight reports missing Permitech settings and other registration blockers. Do not rely on the Permitech card’s saved or tested state to verify these flows in the current release.

​
Update, rotate, or remove credentials

  • Update or remove an in-app record — changes the personal or workspace record represented by the Permitech card. Under the current limitation, this does not change the credentials used by dataset import or registration.
  • Rotate the effective key — have the deployment operator replace the configured API key and restart or roll out the affected backend workload as required by your deployment.
  • Disable the effective connection — clearing the deployment settings disables future Permitech imports and registrations.
Removing the Permitech connection does not unregister any metrics already published to the Permitech metrics store. Those metrics remain live until you remove them from the Permitech platform itself.

​
Where to go next