The agent retrieved core positioning and feature information from the homepage and llms.txt, but could not answer the pricing question because Postforge does not publish pricing details on its public pages. The site is partially navigable: it surfaces enough to understand the product concept and positioning, but lacks documentation links, pricing transparency, and self-hosting details needed for a complete evaluation.

• ›Pricing is intentionally opaque: the site uses only the phrase 'predictably, by what you send' with no tiers, rates, free tier, or fixed fees stated. The agent correctly flagged this as a critical gap but could not retrieve what does not exist in a fetchable form.
• ›The homepage and llms.txt together cover what Postforge does and who it targets, but the site offers no linked documentation, comparison table, or about page—forcing the agent to assemble the answer from fragments (homepage + agent setup file) rather than official docs.
• ›Self-hosting is claimed (AGPL-3.0) but not documented: the llms.txt file mentions it without setup instructions, and does not state whether self-hosting includes all cloud features. The agent noted this absence correctly.
• ›The site surfaces an API spec link and signup page but no human-readable user docs or API reference. The agent discovered llms.txt directly via model memory (not surfaced as a link), which was content-bearing; without it, even less would be known.
• ›Positioning claims (vs. Klaviyo/Omnisend/Mailchimp) are stated without comparative data or a feature matrix, making it hard for a prospective user to verify whether the replacement claim is sound.