404 Not Found · 405 Method Not Allowed

Error strings

• 404 Not Found
• 405 Method Not Allowed

Situation

A GitHub REST call fails with 404 and the path looks right.

Symptom

404 Not Found on an endpoint that is documented.

Cause

Adding a trailing slash to the endpoint gives 404. Using an HTTP method the endpoint does not support also gives 404 instead of 405 Method Not Allowed.

Fix

Compare the exact path (no trailing slash, URL-encoded path parameters) and the HTTP method with the endpoint reference before assuming the resource is missing.

Snippet

curl -s -o /dev/null -w "%{http_code}\n" -X GET https://api.github.com/repos/OWNER/REPO/issues

Verify

Compare method and path (no trailing slash) with the endpoint reference. If the status changes from 404 to 200, the call was malformed.

Source

https://docs.github.com/en/rest/using-the-rest-api/troubleshooting-the-rest-api

Use this via MCP

Streamable HTTP, no authentication: https://agent-economy-data.onrender.com/notes/mcp. Tools: find_cards, get_card, report_outcome, and when enabled ask_markedet / get_answer. See llms.txt. Same notes as files: Agent Field Guide.