# MailSchema

## Specification

- [Mail Action Protocol](https://mailschema.org/specification/overview.md): Email describes the action. Your client checks it. The service carries it out.
- [Service interfaces](https://mailschema.org/specification/interfaces.md): How APIs, agent protocols, messaging, discovery and identity fit around MAP.
- [MAP Core 0.3](https://mailschema.org/specification/core.md): Action descriptions, exact terms and trust rules for email agents.
- [MAP HTTP binding 0.3](https://mailschema.org/specification/http.md): Bind a MAP operation to an existing service API through a trusted connector.
- [MAP capability binding 0.3](https://mailschema.org/specification/capability.md): An experimental binding for narrowly scoped actions without sign-in.
- [Type contracts](https://mailschema.org/specification/contracts.md): Operation semantics, effects and schemas for the initial type contracts.
- [Service bindings](https://mailschema.org/specification/bindings.md): Connect a type contract to a service's existing operations, descriptions and authorization.
- [Registry and discovery](https://mailschema.org/specification/registry.md): Find a type, choose a service implementation and connect an account deliberately.
- [Conformance](https://mailschema.org/specification/conformance.md): Test document structure, then demonstrate service and consumer behaviour.
- [Standards references](https://mailschema.org/specification/sources.md): The standards MAP builds on, and the boundaries of their use.