Tabidoo API

Setup

Wiring Tabidoo by hand means generating a JWT bearer token in the app settings, sending it on every call, and threading app and table ids through nested data routes yourself. Through Jentic you install once, import Tabidoo from the API Directory, store the token once, and your agent calls it.

Permission scoping

Tabidoo puts the app id and table id in the URL path (/apps/{app_id}/tables/{table_id}/...), so a rule can pin your agent to one table: it can read or add data there and nothing else. You choose the operations it may call, so writes are not included unless you add them.

Credential isolation

Your Tabidoo JWT 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 'list tables in an app' or 'filter table data', and Jentic returns the matching Tabidoo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.