Walls.io API

Setup

Wiring the Walls.io API by hand means passing your access_token as a query parameter on the api.walls.io/v1 host and attaching it to every request yourself. Through Jentic you install once, import the Walls.io API from the API Directory, store the access token once, and your agent calls it.

Permission scoping

The Walls.io API puts the post id in the URL path (/posts/{postId}), so a rule can pin your agent to one post. You choose the operations it may call, so you can allow reading posts and creating a native post while an update to an existing post is not included unless you add it.

Credential isolation

Your Walls.io access 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 native post' or 'list changed posts', and Jentic returns the matching Walls.io API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.