Snipe It Readme Snipe-IT Asset Management

Setup

Wiring Snipe-IT Asset Management by hand means sending your bearer token on every request, filling in your own host in the /api/v1 base, and handling paging across hardware yourself. Through Jentic you install once, import Snipe-IT Asset Management from the API Directory, store the token once, and your agent calls it.

Permission scoping

Snipe-IT puts the asset id in the URL path (/hardware/{id}), so a rule can pin your agent to hardware operations: it can read and create assets and nothing else. You choose the operations it may call, so destructive ones like deleting or overwriting an asset are not included unless you add them.

Credential isolation

Your Snipe-IT Asset Management token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a new asset' or 'look up hardware by asset tag', and Jentic returns the matching Snipe-IT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.