Felt
for LuumenAI
Read Felt maps, layers, and projects — and make map changes as approved steps
Connect Felt and your agent can read the maps your team works from: layer lists, elements as GeoJSON, element groups, projects, and connected data sources. Ask what is on a map before you touch it. When a change is needed — a new project, a duplicated map, updated elements — the agent states the plan and waits for your approval before it writes. Authentication is by API key.
The Felt toolbox
15 tools: 7 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Map DetailsRetrieves comprehensive details of a specific Felt map including title, URL, layers, elements, basemap settings, access permissions, and timestamps.
- ReadGet User DetailsRetrieve information about the authenticated user.
- ReadList Element GroupsRetrieves all element groups from a Felt map.
- ReadList ElementsLists all elements on a specific map as a GeoJSON FeatureCollection.
- ReadList LayersList all layers on a specific map.
- ReadList ProjectsRetrieve a list of projects accessible to the user.
- ReadList SourcesList all data sources (external data connections) accessible to the authenticated user.
- WriteCreate or Update ElementsCreate or update map elements using GeoJSON FeatureCollection format. Approval by default
- WriteCreate ProjectCreate a new Felt project with the specified name and visibility settings. Approval by default
- WriteDelete ElementDelete a specific element from a map. Approval by default
- WriteDelete LayerDelete a specific layer from a map. Approval by default
- WriteDelete MapPermanently deletes a map and all its associated data from Felt. Approval by default
- WriteDelete ProjectDelete a project and all its contents. Approval by default
- WriteDuplicate MapCreates a complete copy of a Felt map including all layers, elements, and configuration. Approval by default
- WriteUpdate ProjectUpdate an existing project's name or visibility. Approval by default
One prompt, start to finish
What a governed Felt run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create or update elements, create project, delete element, delete layer, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Felt — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Felt to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.