What authentication does the Beeminder API use?

Beeminder uses an auth_token sent as a query parameter on every request. You generate the token from your Beeminder account settings. Jentic stores the token in its vault and appends auth_token at execution time so it never enters agent context, and Jentic redacts it from logs.

Can I submit datapoints to a Beeminder goal through the API?

Yes. POST /users/{userId}/goals/{goalSlug}/datapoints.json submits a single datapoint with a value and optional comment, and /users/{userId}/goals/{goalSlug}/datapoints/create_all.json batches several. PUT and DELETE on /users/{userId}/goals/{goalSlug}/datapoints/{datapointId}.json correct or remove a prior entry.

How do I trigger a pledge charge through Jentic?

Search Jentic for derail a Beeminder goal to find POST /users/{userId}/goals/{goalSlug}/shortcircuit.json, which derails immediately and charges the current pledge. For a non-goal-related accountability charge, use POST /charges.json with the amount and note. Both calls execute through Jentic with the auth_token injected from the vault.

Does the Beeminder API let me change a goal's pledge schedule?

Yes. POST /users/{userId}/goals/{goalSlug}/stepdown.json schedules a stepdown to the next-lower pledge after the standard delay, and POST /users/{userId}/goals/{goalSlug}/cancel_stepdown.json cancels a queued stepdown before it takes effect.

What are the rate limits for the Beeminder API?

Beeminder does not document a hard rate limit in the spec; the service is designed for occasional human-scale writes plus tracker integrations. If you receive HTTP 429 responses, back off and retry, and avoid tight polling loops on /refresh_graph since that endpoint runs an expensive recompute server-side.

Can I list a user's archived goals via the API?

Yes. GET /users/{userId}/goals/archived.json returns archived goals for a user, complementing GET /users/{userId}/goals.json for active goals. Use the user_id self to refer to the authenticated user without knowing their numeric ID.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Beeminder operations and credentials the agent may use. Since Beeminder puts the user id and goal slug in the URL path, such as /users/{userId}/goals/{goalSlug}/datapoints.json, you can pin the agent to a single goal so it only submits datapoints there and touches nothing else. You also choose the operations it may call, so destructive ones like shortcircuit, stepdown, and /charges.json stay out of reach unless you explicitly add them.