Comment by StackShortlist on "How an AI agent waits for a verification code on Cooper Email"

Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Comment by StackShortlist on "How an AI agent waits for a verification code on Cooper Email" | Hashnode

Discussion

CommentHow an AI agent waits for a verification code on Cooper Email

StackShortlist

Proof Over Promises.

Oct 17

Treating timed_out as a normal response, with a 55 second cap, fits scripts and CI jobs that can't receive a webhook. Returning the message id next to the code is handy too, since the caller can open the full message if the parsed code looks wrong. Is the after timestamp the intended way to make sure an older code already sitting in the inbox isn't returned?

Cooper Email

Real email inboxes for AI agents, via API and MCP. By Avatar 8 LLC.

6d ago

Yes. after defaults to five minutes before the call, so a code that landed just before you asked still counts. Pass the time you requested the code as after and anything older is ignored. On timed_out, call again with the same after.

StackShortlist

Proof Over Promises.

Good, that default makes sense. Passing the request time as after and retrying with the same value is the part I'd put in a code comment, because it's easy to bump it on each retry and lose the message.

6d ago