Can I manage an app's data and files with the Fine Structure API?

Yes. You can read the file tree, read and write individual source files, and patch or rename them, and separately define data entities and query, create, update, or delete their records. Changes can be staged in a change set, validated, and applied, so an agent can check its edits before they land.

What are the rate limits for the Fine Structure API?

The OpenAPI spec does not state a request rate limit. Generation work is asynchronous and metered by your account plan, so create a job and poll its status rather than busy-waiting, and check the Fine Structure documentation for current limits.

Is there a Fine Structure MCP server?

Yes, Fine Structure exposes an MCP endpoint and a tool manifest. You can also connect Fine Structure directly through Jentic: your agent gets the full 130-endpoint surface without loading another server's tool definitions into its context, your token is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.

Can I limit what my agent is allowed to do with the Fine Structure API?

Yes. Write a rule that allows the read and edit operations your agent needs, such as reading files and querying entities, and leave the record-delete, secret, and domain-removal operations off the list, so an agent can build and inspect an app without removing data or rotating secrets. Every call it makes is recorded in your Jentic One audit log.

How do I build an app with the Fine Structure API through Jentic?

Search Jentic for 'build a web app from a prompt', add the Fine Structure API from the directory, and store your token once; your agent then creates the app, polls the generation job, edits files, and publishes. To run it on your own infrastructure, install Jentic One from its GitHub repo.