The gap between a bad spec and a good one is rarely writing quality; it is whether anyone checked how the thing being integrated with actually works. Giving the architect its own browsing tool means those checks can happen inside the same pass rather than being left as open questions for whoever implements. Start with fast_spec to see whether the shape is right before spending a deep run on it.
Pre.dev's architect agent, reachable as a hosted endpoint. It sits before the code: you describe what you want built and it produces the specification.
- fast_spec — a quick specification pass
- deep_spec — the thorough version
- browser_agent — browse for the context the spec needs
OAuth with PKCE and dynamic registration against api.pre.dev, or an API key header. A credit-based subscription funds the runs.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen