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

Yes. Write a rule that allows only the post create and schedule operations under one workspace id, so the agent can draft and queue posts for that client but cannot publish immediately or remove members, and every call is logged.

What authentication does the BAMF Developer Platform API use?

The BAMF API authenticates with a bearer token, as declared in its OpenAPI spec. Most endpoints require that token; several read-only endpoints, such as the public health check and shared analytics links, need no credential. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

Can I schedule and publish posts across networks with the BAMF API?

Yes. Create a draft post, schedule it for a future time, or publish it immediately, and the same post surfaces in the LinkedIn and X analytics endpoints so the agent can read how each network performed.

How do I schedule a social post through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the BAMF API from the Jentic API Directory and store your bearer token. Your agent searches for 'schedule a social post' and Jentic returns the schedule operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the BAMF Developer Platform API?

The BAMF OpenAPI spec does not define rate limits. Generation and outreach run as asynchronous jobs you poll, so throughput depends on job processing rather than a fixed per-second ceiling; check your BAMF plan for current limits.