Swetrix API

Setup

Wiring the Swetrix API by hand means passing its API-key request header on every call against api.swetrix.com and managing its log, project, and organisation routes yourself. Through Jentic you install once, import the Swetrix API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Swetrix API puts each resource id in the URL path (/v1/project/{id}, /v1/organisation/{orgId}), so a rule can pin your agent to one project or organisation: it can read its analytics and update that record and nothing else. You choose the operations it may call, so destructive ones like deleting a project or an organisation are not included unless you add them.

Credential isolation

Your Swetrix API key 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 'get traffic analytics data' or 'fetch a project funnel', and Jentic returns the matching Swetrix API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.