Can I create a native post with the Walls.io API?

Yes. Use the POST /posts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Walls.io API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a native post through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a native post'. Jentic returns the matching Walls.io API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Walls.io API have?

The Walls.io API exposes 15 endpoints covering analytics, media, posts operations.

Can I limit what my agent is allowed to do with the Walls.io API?

Yes. Because you self-host Jentic One, your own rules decide which Walls.io operations and credentials the agent may use. You can allow it to read posts with GET /posts and create a native post with POST /posts while leaving out updates to an existing post via PUT /posts/{postId} unless you add that. Since the post id sits in the URL path (/posts/{postId}), a rule can also pin the agent to a single post.