AI-driven management

Hand the building over to an agent.

A bearer-token API lets a program create pages, stock a store, set up a questionnaire or adjust your colours. Each area is a separate role that you grant and revoke on its own.

1. A manual generated from the code, served at the root address
2. Every route states the permission it requires
3. Eight roles: pages, store, menus, design, emails…
4. Tokens stored hashed: a leaked database grants no access

1. Expiry dates and IP address restrictions
2. A log of every call
3. No page deletion, ever
4. An unknown key is refused, never silently ignored

How it is set

The guide is generated from the router and the view classes: it cannot describe a route that does not exist, or leave a permission unsaid. This very page was built through the API.

The manual — the first call to make

GET /api/agent/v1/
Authorization: Bearer jk_ag_…

{ "version": {"numero": "1"},
"points_d_entree": [
{"chemin": "/api/agent/v1/pages/creer/",
"methodes": "POST",
"permission": "administration_pages.add_page",
"role": "Create a page. It starts as a draft."}
],
"catalogue_des_blocs": { … } }

What the agent is allowed to do

GET /api/agent/v1/qui-suis-je/

{ "roles": ["Page editor agent"],
"peut": {
"creer_une_page": true,
"modifier_une_page": true,
"supprimer_une_page": false
} }

To connect Claude — on claude.ai, in the mobile app or in Claude Code — follow the guide Connect Claude to your site.