canonical: https://jentic.com/apis/postman-echo.com/postman-echo

# Postman Echo Login API

The Postman Echo Login API describes a single mock login request against the public Postman Echo service, a test endpoint that echoes what it receives. It sends a JSON body with a username and password to the /post route and expects a 200 Success response, which makes it useful for checking that an HTTP client, agent, or test harness builds and sends a JSON POST correctly. It needs no account or key and performs no real authentication, so it is a fixture for testing request plumbing rather than a login service.

## For AI agents

Send a mock JSON login request with a username and password to the public Postman Echo /post route to test that an HTTP client or agent builds a POST correctly.

## Scope

Does not authenticate real users, issue sessions, or store data. Use for testing that a JSON POST request is built and delivered only.

## Capabilities

- Send a JSON POST with username and password fields to the Postman Echo /post route
- Verify that an agent or HTTP client serialises a JSON request body and reaches a live endpoint
- Exercise a login-shaped request in a test suite without touching a real identity provider
- Smoke-test outbound HTTPS connectivity from an agent runtime with a keyless public endpoint

## Use cases

### First call for a new Jentic setup

A developer who has just installed Jentic wants proof that their agent can find and execute an operation end to end before wiring a real API. Postman Echo needs no account or key, so the agent searches Jentic for a mock login, loads the single POST /post operation, and sends a test username and password. A 200 Success confirms that discovery, request building, and outbound HTTPS all work.

Example prompt: Search Jentic for 'send a mock login request', load POST /post, and send username testuser with password Password@123, then confirm a 200 response

### HTTP client regression tests

A team maintaining an HTTP client library needs a stable public endpoint to check JSON POST handling in continuous integration. The Postman Echo login fixture gives a known route, a fixed login-shaped body, and an expected 200 response, so a failing run points at the client rather than at an authentication backend.

Example prompt: Send POST /post with a JSON body containing username and password and fail the check unless the status code is 200

### Teaching login request structure

In a tutorial on calling REST APIs, learners need to practise sending credentials-shaped JSON without risking real accounts. The mock login request shows the shape of a username and password body sent to a POST route, with no real authentication happening on the other side.

Example prompt: Build a JSON body with username and password, send it to POST /post on https://postman-echo.com, and print the response status

## Key resources

- **Mock login** — Single POST /post operation that accepts a username and password JSON body

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 94 / 100
  - Developer Experience & Jentic Compatibility: 81 / 100
  - AI-Readiness & Agent Experience: 17 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 25 / 100
- **View full report:** https://jentic.com/apis/postman-echo.com/postman-echo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Postman Echo needs no auth, so the setup cost is the plumbing: building the JSON body, setting the content type, and pointing at the right host. Through Jentic you install once, import Postman Echo from the API Directory, and your agent calls it, which also proves your Jentic setup works before you add a real API.
- **Permission scoping:** The spec exposes one operation, POST /post, so a rule allowing it is the whole surface. It is a useful baseline for seeing rules and the call log in action before you scope an API with more at stake.
- **Credential handling:** Postman Echo takes no API key or token, so there is nothing for your Jentic One instance to store. The test username and password travel in the request body you choose to send.
- **Discovery method:** Agents search Jentic by intent such as 'send a mock login request' or 'test a JSON POST', and Jentic returns the Postman Echo operation with its input schema so the agent sends a well-formed body.

## Related APIs

- **httpbin** — Public HTTP request and response testing service with many inspection routes
- **GoRest API** — Fake REST API with users, posts, and comments for testing
- **Postman API** — Manage Postman collections, environments, and monitors

## FAQ

### What authentication does the Postman Echo Login API use?

None. The OpenAPI spec declares no security scheme and an empty security list, so POST /post is called without any key or token. The username and password in the request body are test values for a mock login, not credentials checked against an account.

### What does the Postman Echo Login API return?

The spec declares a single 200 Success response and does not define a response schema. Postman Echo is a public echo service, so treat the call as a check that your request was built and delivered rather than as a login that returns a session.

### What are the rate limits for the Postman Echo Login API?

The OpenAPI spec does not specify rate limits. Postman Echo is a shared public test service served from https://postman-echo.com, so keep test traffic light and avoid using it for load testing.

### Is there a Postman Echo MCP server?

You don't need an MCP server to give your agent Postman Echo. Jentic connects it directly from the API Directory: import it and your agent can call the mock login operation straight away, with no key to set up and no extra tool definitions loaded into its context.

### Can I limit what my agent is allowed to do with Postman Echo?

Yes, though there is little to limit: the spec has one operation, POST /post. A rule that allows only that operation keeps the agent to the mock login, and every call it makes is logged, which is handy when you are checking how an agent behaves on its very first request.

### How do I send the mock login through Jentic?

Search Jentic for 'send a mock login request', load the POST /post operation, and execute it with a JSON body containing a username and password such as testuser and Password@123. To run it on your own infrastructure, install Jentic One from its GitHub repo.