"startTime": "2026-07-23T00:00:00Z", "endTime": "2026-07-24T00:00:00Z",
We need also the option to have timeframe like 24h / 6h and not specific times for the scheduled use case
"startTime": "2026-07-23T00:00:00Z", "endTime": "2026-07-24T00:00:00Z",
We need also the option to have timeframe like 24h / 6h and not specific times for the scheduled use case
models
Maybe it should be 'model' and not models ? :)
Scheduled
Maybe we also need a status? Active / Inactive or something like that So it will be easy to temporarily stop the job from running for some reason instead of deleting it. wdyt?
location
Maybe this can be optional parameter, so if it is not specified the full model are is returned
Resolved model/region echo (to discuss)¶
If the model is specified in the request how can it get a different source. I think if the bb doesn't fit the model bb it should return an error. wdyt?
status
Can you please add description for each status, I'm not sure I understand correctly the differences between them.
remaining quota in body
What does it mean to have it in the headers like what we have for credits and rate limits? is it a small task or better to keep it for later?
Tickets
Can we please add another ticket for adding the new endpoints to the MCP once they are ready?
Server-managed session_id (Redis turn persistence) deferred to Phase 2.
In that case, isn't it better to have in the request the option to pass the conversation history from the client, like what we already have (if I got it correctly)
Gale
How do we handle 'Gale' as a real word not referring to our agent name? Maybe worth validating if there is any use in Gale name and if not, not implementing this moderation?
free-text name uses the locations agent
Do you mean it search only in the account location names?
Deferred to Phase 2 — the studio-blocks link is not yet persistent. Phase 1 returns the map link only.
What will be the link? just a link to the platform map, no context for the asked question right?