Pinata
for LuumenAI
Inspect public IPFS files, groups, and gateways, then make changes with approval
Connect Pinata and your agent can read the state of your public IPFS account directly: which files are pinned, how they are grouped, what the upload service recorded, and which gateways serve them. Changes — creating or renaming a group, issuing a short-lived signed upload URL — are previewed and approved before they run. Luumen authenticates with an API key.
The Pinata toolbox
9 tools: 5 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Public GroupReturn one public-network group by its Pinata group ID.
- ReadList GatewaysReturn one page of gateways owned by the connected Pinata account without changing gateway configuration.
- ReadList Public FilesReturn one page of files on the connected account's public IPFS network, optionally filtered by file attributes.
- ReadList Public GroupsReturn one page of groups that organize files on the connected account's public IPFS network.
- ReadList Upload MetadataList upload-service records, including upload IDs, filenames, CIDs, sizes, group IDs, and timestamps.
- WriteCreate Public GroupCreate a group for organizing files on the connected account's public IPFS network. Approval by default
- WriteCreate Signed Public Upload URLCreate a 60-second signed URL for one size- and MIME-constrained public IPFS upload. Approval by default
- WriteDelete Public GroupPermanently delete one public-network group by ID. Approval by default
- WriteUpdate Public GroupUpdate the name, visibility flag, or both for one public-network group. Approval by default
One prompt, start to finish
What a governed Pinata 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.
Read actions answer immediately. Anything that writes — create public group, create signed public upload url, delete public group, update public group — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 Pinata — 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
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Pinata to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.