11–14 of 14 posts
Earlier quoted context omitted.
Awesome. I’ll check it out. Sometimes validation is a number though
thats a good point. I could also include the email body in the api response. Then you could regex to get the code. Later on i could layer in a ai parser to extract the code and just return that.
I integrated it into an MCP server. you can test it at https://mcp.profullstack.com
Earlier quoted context omitted.
Awesome. I’ll check it out. Sometimes validation is a number though
thats a good point. I could also include the email body in the api response. Then you could regex to get the code. Later on i could layer in a ai parser to extract the code and just return that.
Earlier quoted context omitted.
thats a good point. I could also include the email body in the api response. Then you could regex to get the code. Later on i could layer in a ai parser to extract the code and just return that.
would be cool to parse validation codes, urls and phone numbers perhaps all metadata like contact info too.
Earlier quoted context omitted.
would be cool to parse validation codes, urls and phone numbers perhaps all metadata like contact info too.
The email body is now returned in the api as you asked for. In order to do the parsing I would be making an openai chat api call...so that would be for paid users only. Thats reasonable right?