Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rede Ideias na Mesa API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fideiasnamesa.com.br%2Fideiasnamesa" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fideiasnamesa.com.br%2Fideiasnamesa" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Rede Ideias na Mesa API.
Log a member in with email and password and receive a JWT accessToken and refreshToken
Renew an expired access token with POST /auth/refresh before the session lapses
Register a new member account with email, name, username, and password
Update the signed-in member's profile fields such as bio, city, state, workArea, and instagram
GET STARTED
List platform users as an admin, filtered by userType, active status, or a search term
Reactivate a deactivated user account by id as an admin
Patterns agents use Rede Ideias na Mesa API for, with concrete tasks.
★ AI agent managing member profiles through Jentic
A developer supporting the Rede Ideias na Mesa community wants their agent to keep a member's public profile current without hand-coding the token flow. Through Jentic the agent searches for 'update my profile', loads the PATCH /profiles operation with its input schema, and sends the changed fields such as bio, city, and workArea with the bearer token attached at call time. The agent then reads GET /profiles to confirm the update.
Call PATCH /profiles with bio set to a new two-line summary, city set to Recife, and state set to PE, then GET /profiles to confirm the saved values
Session handling for a companion app
A mobile or web companion app signs members in and keeps them signed in. The app posts email and password to /auth/login, stores the returned accessToken and refreshToken, and calls /auth/refresh with the refreshToken when the JWT expires, which the spec states happens after 15 minutes. Logging out calls /auth/logout to end the session.
POST /auth/login with email and password, then POST /auth/refresh with the returned refreshToken and use the new accessToken to call GET /auth/me
Admin user review
Platform administrators review who has joined and restore accounts that were closed by mistake. GET /users returns a paged list filterable by userType (COMUM, ADMIN, or PREMIUM), active, and a search term, and PATCH /users/{id}/reactivate brings a deactivated account back. GET /users/{id} returns the full record before any change.
Call GET /users with active set to false and search set to a member's name, then PATCH /users/{id}/reactivate for the matching id
Password recovery support
Members who forget their password need a self-service reset. POST /auth/forgot-password sends a reset request for an email, and POST /auth/reset-password completes it with the token and newPassword. A signed-in member can instead change it directly with PATCH /users/me/password using currentPassword and newPassword.
POST /auth/forgot-password with the member's email, then POST /auth/reset-password with the token from the reset email and a newPassword
17 endpoints — the rede ideias na mesa api handles member accounts for the rede ideias na mesa platform, a brazilian network for food and nutrition education.
METHOD
PATH
DESCRIPTION
/auth/login
Log in and receive access and refresh tokens
/auth/refresh
Renew the access token
/auth/me
Get the signed-in user
/users
Register a new user
/users
List users (admin)
/profiles
Update the signed-in member's profile
/users/{id}/reactivate
Reactivate a user (admin)
/auth/login
Log in and receive access and refresh tokens
/auth/refresh
Renew the access token
/auth/me
Get the signed-in user
/users
Register a new user
/users
List users (admin)
/profiles
Update the signed-in member's profile
/users/{id}/reactivate
Reactivate a user (admin)
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Rede Ideias na Mesa API by hand means posting credentials to /auth/login, holding a short-lived JWT, and calling /auth/refresh with the refreshToken before it lapses. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Most member operations act on the signed-in user through /me and /profiles paths, while admin routes put the user id in the path (/users/{id}), so a rule can allow the member operations and leave every admin route out. You choose the operations it may call, so destructive ones like DELETE /users/me/deactivate are not included unless you add them.
Credential isolation
Your Rede Ideias na Mesa credential 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 'update my profile' or 'refresh my access token', and Jentic returns the matching Rede Ideias na Mesa operation with its input schema so the agent calls the right endpoint without browsing the Portuguese reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Rede Ideias na Mesa API through Jentic.
What authentication does the Rede Ideias na Mesa API use?
The Rede Ideias na Mesa API uses a bearer JWT in the Authorization header, per its OpenAPI spec. You obtain the accessToken by posting email and password to /auth/login, and the spec notes the token expires after 15 minutes, so renew it with the refreshToken at /auth/refresh. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time.
Can I update a member's profile with the Rede Ideias na Mesa API?
Yes, for the signed-in member. PATCH /profiles accepts phone, bio, profilePhoto, state, city, workArea, instagram, facebook, and linkedin, and GET /profiles reads the current values. Username and password changes use PATCH /users/me/username and PATCH /users/me/password.
What are the rate limits for the Rede Ideias na Mesa API?
The OpenAPI spec does not specify rate limits. Check the platform at https://ideiasnamesa.com.br for current limits and terms of use.
Is there a Rede Ideias na Mesa MCP server?
You don't need an MCP server to give your agent the Rede Ideias na Mesa API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the account and profile operations it needs, discovered on demand.
Can I limit what my agent is allowed to do with the Rede Ideias na Mesa API?
Yes. For example, write a rule that allows only GET /profiles and PATCH /profiles, so the agent can read and edit the member's profile but cannot change the password, deactivate the account, or call admin user routes. Every call it makes is logged.
How do I read the signed-in member through Jentic?
Search Jentic for 'get the signed-in user', load the GET /auth/me operation, and execute it; Jentic attaches the bearer token for you. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Know of an official OpenAPI document? Contribute it →
For Agents
Log in to Rede Ideias na Mesa, refresh the short-lived JWT, and read or update a member's profile, or list and reactivate users as an admin.
Use for: Log in to Rede Ideias na Mesa with my email and password, Refresh my access token before it expires, Get the profile of the signed-in member, I want to update my bio and city on my profile
Not supported: Does not serve recipes, nutrition data, courses, or forum content. Use for Rede Ideias na Mesa member login, sessions, and profiles only.
The Rede Ideias na Mesa API handles member accounts for the Rede Ideias na Mesa platform, a Brazilian network for food and nutrition education. It registers users, logs them in with email and password to issue a JWT accessToken and a refreshToken, renews and revokes sessions, and runs the forgot-password and reset-password flow. Members can read and update their own profile, including bio, city, state, workArea, and social links, while admins list users by userType and reactivate accounts.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>