togetajob.com
Finalizing the report
Preparing the stored Is Agentic score
togetajob.com
Preparing the stored Is Agentic score
togetajob.com
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 17 applicable checks
Strong
Weighted across 12 applicable checks
Strong
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
Declare scoped API permissions where machines can read them: named OAuth scopes in your OpenAPI security schemes, or scopes_supported in RFC 9728 protected-resource metadata. Prose descriptions of roles help humans, but agents need the machine-readable declaration to request least-privilege access.
Expose a public REST or GraphQL API. AI agents need programmatic access - not just a web UI - to integrate with your product.
Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.
Checks are grouped by relevance for App sites.
Homepage: 10942 chars, semantic headings (1 H1 + 21 H2s + 5 H3s), 10.0% content ratio. 5 of 5 sampled inner pages have text without JavaScript.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh or JavaScript-redirect stubs across 23 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
OpenAPI spec found at https://togetajob.com/data/openapi.json (version: 3.1.0)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
OpenAPI declares security schemes but no named OAuth scopes - agents get all-or-nothing access. Declare per-scope grants (e.g. read:*, write:*) in the spec.
How to pass
Declare scoped API permissions where machines can read them: named OAuth scopes in your OpenAPI security schemes, or scopes_supported in RFC 9728 protected-resource metadata. Prose descriptions of roles help humans, but agents need the machine-readable declaration to request least-privilege access.
API returns JSON error responses (404 at https://togetajob.com/api/v1/orank-probe-test)
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://togetajob.com/sitemap.xml with 1977 entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block)
Pricing structured data found on the homepage: an offer priced 0 USD (free)
API/docs link found on homepage and resolves: /developers
All metadata signals present: canonical URL, lang="en", og:image, og:type
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 8 measured pages fit an agent context budget (largest ~3K tokens)
API described in documentation at https://togetajob.com/developers.md but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7.
How to pass
Expose a public REST or GraphQL API. AI agents need programmatic access - not just a web UI - to integrate with your product.
Verified live: GET https://togetajob.com/data/exams.json answered 200 without credentials (zero-auth access). Described but not verified live: self-serve key generation
How to pass
Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.
MCP server connected via Streamable HTTP - togetajob v1.0.0 (protocol 2025-11-25)
The live API operation https://togetajob.com/api/health returns IETF RateLimit headers: ratelimit-limit, ratelimit-policy, ratelimit-remaining.
OpenAPI defines a typed error schema in components.schemas and 4xx/5xx responses reference it
API versioning strategy found (URL versioning) with Deprecation and Sunset headers documented at https://togetajob.com/developers.md
CLI package found on npm: togetajob
100% of operations define typed response schemas, 100% use application/json
REST: agent-friendly schema (34 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 34/34 ops with IDs, 24/34 with typed schemas
NPM package found: togetajob - "togetajob.com — the free guide to NYC government jobs and civil service exams, and how to get a job in New York City. Exam windows, entry-level job guides, and open postings from the site's public data, scriptable."
MCP manifest has full branding (name, icon, description) at https://togetajob.com/mcp/server-card
MCP server card served at https://togetajob.com/mcp/server-card
RFC 8288 Link header advertises: describedby, service-desc, service-doc
Full markdown fallback support. Homepage (https://togetajob.com/index.md) and all 3 sampled content pages return markdown: https://togetajob.com/about.md, https://togetajob.com/exams/7066.md, https://togetajob.com/jobs/deputy-commissioner-bureau-of-water-sewer-operations-administrative-engineer-m7-805320.md
95% of 500 sampled sitemap entries carry lastmod; newest is 1 day(s) old
Found the llms.txt at https://togetajob.com/llms.txt.
The llms.txt is well-formatted: 79 lines with markdown links, 12,592 characters in total.
When-to-use guidance found in llms.txt
Entity linking to github.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, Crunchbase or GitHub)
How to pass
Add sameAs links in your JSON-LD structured data pointing to your profiles on Wikipedia, Wikidata, LinkedIn, Crunchbase or GitHub. This helps AI disambiguate your brand from similarly named entities.
Schema types that match what the homepage shows: FAQPage. Lists on the homepage with no schema type: "Where in NYC?" (3 items), "File for the exam in time" (3 items), "Be patient, you got this" (13 items)
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://togetajob.com/index.md serves markdown
Code fences balanced across 2 markdown documents
Developer portal found at /developers
RFC 9727 api-catalog with 2 API link(s) and rfc9727 profile
Path-suffix markdown docs served with text/markdown content-type: /developers.md, /index.md
All 3 tools on product MCP have detailed descriptions (>= 20 chars)
3/3 tools on product MCP have parameter schemas (2 take no parameters), 1 with required fields
product MCP identifies as "togetajob" v1.0.0 with instructions
product MCP exposes 3 tools - substantial tool surface
All 3 tool names follow consistent convention, descriptive, and non-generic
product MCP returns structured JSON-RPC errors with code and message
product MCP uses modern Streamable HTTP transport
Offset/page-based pagination found in OpenAPI spec - consider migrating to cursor-based pagination for agent friendliness
How to pass
Use a consistent, documented pagination shape on your list endpoints (cursor-based preferred) and define the pagination fields in your OpenAPI response schemas, so agents can page through results without guessing the shape.
SDK packages found across 3 ecosystems: npm, pypi, go
product MCP: 3/3 tools have behavioral annotations (readOnlyHint/destructiveHint)
MCP server card found at https://togetajob.com/mcp/server-card (server-card extension, all required fields)
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
156 native controls, 1 non-native div-soup affordances (99% native).
154/155 interactive elements have a computable accessible name (99%).
3/3 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does togetajob.com do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does togetajob.com do and who is it for? Explain it back to me.
4 steps1 reasoning step
The agent satisfied the task by fetching the homepage, About page, and free-exams page, assembling a comprehensive explanation of what togetajob.com does, who it serves, how it's priced, and how it positions itself. The site is reasonably navigable and self-explanatory, though it leaves several key details (owner identity, revenue model, sorting criteria, five-question quiz content) undocumented.