AmunCore

AmunCore turns a database into a secure REST API without writing a backend. You connect a database, pick tables, and endpoints go live with routing, authentication, validation, pagination, joins, errors, logs and docs already handled — the layer between a database and HTTP that would otherwise be a two-to-six-week project. It supports SQL Server, MySQL, MariaDB, PostgreSQL, Oracle and SQLite, with a visual builder that is the same regardless of the engine underneath. It is MCP-native by design: the endpoints you build become tools an AI assistant can call under the same keys, permissions and audit trail, and the MCP endpoint is live, token-gated and now fronted by RFC 8414/9728 OAuth discovery. A public OpenAPI 3.0.1 describes the five generated CRUD operations; REST auth is an X-Api-Key header. Built and operated by HYNOWorld, with a self-hosted option for regulated deployments. Full CRUD, a free plan forever, and paid tiers from $29/mo.

AmunCore publishes 1 API contract indexed on the APIs.io network: Dynamic API. Tagged areas include Database, API Management, Backend, No-Code, and SQL.

The AmunCore catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

AmunCore’s developer surface includes documentation, code examples, authentication, sandbox, pricing, signup flow, support, and 30 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

56.2/100 strong ▬ flat Agent 57/100 agent ready Front door AI 6/6 dominant saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

2 published contracts 1 MCP Servers 3 Agent Skills

Database API Management Backend No-Code SQL PostgreSQL MySQL Oracle MCP Agents Data SQL Server Webhook OpenAPI Low-Code Egypt

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 56.2/100 · strong

Contract Quality 11.6 / 19

Developer Ergonomics 5.3 / 15

Access Clarity 12.5 / 15

Operational Transparency 3.5 / 10

Contract Governance 2.9 / 9

Discoverability 5.0 / 8

Regulatory Posture 5.0 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 57/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/amuncore/"><img src="https://apis.io/badge/amuncore/card.svg" alt="AmunCore on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's Ask about this →
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter Ask about this →
Well-Known Catalog +4 pts — common[].type includes WellKnown, APICatalog, or api-catalog Ask about this →

1 more unmet check in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 35.1 — up to +13.0 composite points Ask about this →
Contract Quality scores 61.7 — up to +9.6 composite points Ask about this →
Operational Transparency scores 35.7 — up to +8.4 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/amuncore/apis.yml: open an issue on github.com/api-evangelist/amuncore to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 5

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

AmunCore Dynamic API

Generated CRUD over a table or view exposed as an endpoint on a registered AmunCore application.

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

AmunCore API Engine: Dynamic API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

AmunCore MCP Server

AmunCore is MCP-native by design: the REST endpoints a user builds over their own database become tools an AI assistant can call, under the same keys, permissions and audit trai...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Expose a database table as an API over MCP

AGENT SKILL

Query a table through an AmunCore endpoint

AGENT SKILL

Create, update and delete a record safely

AGENT SKILL

AmunCore API pricing

Prices published by AmunCore, read 2026-10-28 from amuncore.com/#pricing.

Plan	Price
Free	$0 Includes: 1 application, 2 endpoints; 1,000 calls a month; SQL Server; 50 MB of documents; AI assistants
Starter	$29 Includes: 3 applications, 20 endpoints each; 100,000 calls a month; SQL Server and MySQL; 1 GB of documents; A
Pro	$99 Includes: Unlimited applications and endpoints; 5 million calls a month; Every supported database; 3 client co
Enterprise	Custom Includes: Everything in Pro; Unlimited calls and storage; 50 client connectors, 10,000 clients each; Your own

Plan details, limits and sources →

Rate limits

Free plan call quota: 1000 api calls
Starter plan call quota: 100000 api calls
Pro plan call quota: 5000000 api calls

All 4 limits →

Billed by: subscription · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

AmunCore Plans Pricing

4 plans

PLANS

AmunCore Price Estimates

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

AmunCore Rate Limits

4 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

AmunCore

8 quoted statements, read from AmunCore's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

AmunCore

12 quoted statements, read from AmunCore's own page on 2026-11-09.

PRIVACY

FinOps 1

Cost, billing, and metering signals for API financial operations.

AmunCore Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Amuncore Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

AmunCore API Rules

58 rules · 56 error-severity 1 warn-severity 1 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

AmunCore Dynamic Api Overlay

8 actions · update · amuncore-dynamic-api-openapi.yml

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

AmunCore Authentication

apiKey/oauth2 · 3 schemes

SECURITY

AmunCore Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

AmunCore Trust Center

trust center published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

AmunCore Scopes

1 scope · authorizationCode

1 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

AmunCore Agentic Access

5 operations · 3 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Sandbox

Sandbox

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

OpenAPI

OpenAPI

Agent Surfaces 7

MCP servers, agent skills, and machine-readable catalogs

MCPServer

AgenticAccess

LLMsTxt

LLMsTxt

WellKnown

MCPServer

AgentSkill

Scroll for all 7

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

DataModel

Conformance

Webhooks

Build 3

SDKs, sample code, and the tooling you integrate with

Examples

Examples

ToolCrosswalk

ToolCrosswalk

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

TrustCenter

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 5

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

UsageTerms

Company 2

The organization behind the API

Website

Website

About

About

Other 3

Properties that don't map to a standard resource type

Overlay

Overlay

Overlay

Overlay

DataProcessing

DataProcessing

Source (apis.yml)

aid: amuncore
url: https://raw.githubusercontent.com/api-evangelist/amuncore/refs/heads/main/apis.yml
name: AmunCore
description: 'AmunCore turns a database into a secure REST API without writing a backend. You connect a database, pick tables,
  and endpoints go live with routing, authentication, validation, pagination, joins, errors, logs and docs already handled
  — the layer between a database and HTTP that would otherwise be a two-to-six-week project. It supports SQL Server, MySQL,
  MariaDB, PostgreSQL, Oracle and SQLite, with a visual builder that is the same regardless of the engine underneath. It is
  MCP-native by design: the endpoints you build become tools an AI assistant can call under the same keys, permissions and
  audit trail, and the MCP endpoint is live, token-gated and now fronted by RFC 8414/9728 OAuth discovery. A public OpenAPI
  3.0.1 describes the five generated CRUD operations; REST auth is an X-Api-Key header. Built and operated by HYNOWorld, with
  a self-hosted option for regulated deployments. Full CRUD, a free plan forever, and paid tiers from $29/mo.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/amuncore.png
created: '2026-08-03'
modified: '2026-09-16'
specificationVersion: '0.23'
type: Index
position: Producing
access: 3rd-Party
kind: contract
tags:
- Database
- API Management
- Backend
- No-Code
- SQL
- PostgreSQL
- MySQL
- Oracle
- MCP
- Agents
- Data
- SQL Server
- Webhook
- OpenAPI
- Low-Code
- Egypt
tags_raw:
- Database
- API Management
- Backend
- No Code
- SQL
- PostgreSQL
- MySQL
- Oracle
- MCP
- Agents
- Data
- SQL Server
- Webhooks
- OpenAPI
- Low Code
- Egypt
apis:
- aid: amuncore:amuncore-dynamic-api-api
  name: AmunCore Dynamic API
  description: Generated CRUD over a table or view exposed as an endpoint on a registered AmunCore application.
  humanURL: https://amuncore.com
  tags:
  - Dynamic API
  properties:
  - type: OpenAPI
    url: openapi/amuncore-dynamic-api-api-openapi.yml
  - type: Website
    url: https://amuncore.com
  - type: Documentation
    url: https://amuncore.com/swagger
  - type: Examples
    url: examples/amuncore-dynamic-api-examples.yml
  - type: Authentication
    url: authentication/amuncore-authentication.yml
  - type: OAuthScopes
    url: scopes/amuncore-scopes.yml
  - type: Conventions
    url: conventions/amuncore-conventions.yml
  - type: ErrorCatalog
    url: errors/amuncore-problem-types.yml
  - type: RateLimits
    url: rate-limits/amuncore-rate-limits.yml
  - type: DataModel
    url: data-model/amuncore-data-model.yml
  - type: ToolCrosswalk
    url: mcp/amuncore-tool-crosswalk.yml
  - type: Webhooks
    url: asyncapi/amuncore-webhooks.yml
  - type: Plans
    url: plans/amuncore-plans-pricing.yml
common:
- type: Overlay
  url: overlays/amuncore-dynamic-api-overlay.yaml
- type: MCPServer
  url: mcp/amuncore-mcp.yml
- type: AgenticAccess
  url: agentic-access/amuncore-agentic-access.yml
- type: DomainSecurity
  url: security/amuncore-domain-security.yml
- url: https://amuncore.com
  type: Website
- url: https://amuncore.com/swagger
  type: Documentation
- url: https://amuncore.com/llms.txt
  type: LLMsTxt
- url: openapi/_original/amuncore-dynamic-api-openapi.yml
  type: OpenAPI
- url: examples/amuncore-dynamic-api-examples.yml
  type: Examples
- url: overlays/amuncore-dynamic-api-overlay.yaml
  type: Overlay
- url: llms/amuncore-llms.txt
  type: LLMsTxt
- url: well-known/amuncore-well-known.yml
  type: WellKnown
- url: mcp/amuncore-mcp.yml
  type: MCPServer
- url: mcp/amuncore-tool-crosswalk.yml
  type: ToolCrosswalk
- url: skills/_index.yml
  type: AgentSkill
- url: authentication/amuncore-authentication.yml
  type: Authentication
- url: scopes/amuncore-scopes.yml
  type: OAuthScopes
- url: conventions/amuncore-conventions.yml
  type: Conventions
- url: errors/amuncore-problem-types.yml
  type: ErrorCatalog
- url: rate-limits/amuncore-rate-limits.yml
  type: RateLimits
- url: lifecycle/amuncore-lifecycle.yml
  type: Lifecycle
- url: data-model/amuncore-data-model.yml
  type: DataModel
- url: conformance/amuncore-conformance.yml
  type: Conformance
- url: security/amuncore-trust-center.yml
  type: TrustCenter
- url: sandbox/amuncore-sandbox.yml
  type: Sandbox
- url: asyncapi/amuncore-webhooks.yml
  type: Webhooks
- url: packages/amuncore-packages.yml
  type: Packages
- url: plans/amuncore-plans-pricing.yml
  type: Plans
- url: https://amuncore.com/#pricing
  type: Pricing
- url: https://amuncore.com/Register
  type: SignUp
- url: https://amuncore.com/Auth/Login
  type: Login
- url: https://amuncore.com/terms.html
  type: TermsOfService
- url: https://amuncore.com/privacy.html
  type: PrivacyPolicy
- url: https://amuncore.com/#contact
  type: Support
- url: https://amuncore.com/about.html
  type: About
- type: UsageTerms
  url: terms/amuncore-terms-of-service.yml
- type: DataProcessing
  url: privacy/amuncore-privacy-policy.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
X-Discovery:
  date: '2026-08-03'
  method: probed
  note: Found while researching a separate company and profiled on its own merits. Everything below was fetched.
  findings:
  - surface: Website
    url: https://amuncore.com
    http_status: 200
    real: true
  - surface: MCPServer
    url: https://amuncore.com/mcp
    http_status: 401
    real: true
    note: 'Real and well built. GET returns 405; POST jsonrpc returns a correct JSON-RPC error -32001 "Unauthorized: missing
      MCP-Token header" rather than an HTML page.'
  - surface: OpenAPI
    url: https://amuncore.com/openapi.json
    http_status: 404
    real: false
    note: SUPERSEDED — see the 2026-08-10 re-probe below. On 2026-08-03 none was published for the platform itself. Note the
      product GENERATES APIs per tenant, so a platform-level spec is a different thing from the specs it produces.
  - surface: LlmsTxt
    url: https://amuncore.com/llms.txt
    http_status: 404
    real: false
    note: SUPERSEDED — see the 2026-08-10 re-probe below.
  - surface: Control
    url: https://amuncore.com/zzz-control-nonsense
    http_status: 404
    real: false
    note: Control path correctly 404s — no SPA catch-all, so the probes above are trustworthy.
X-Reprobe:
  date: '2026-08-10'
  method: probed
  note: 'Re-probed on the second enrichment pass. AmunCore shipped a machine-readable contract surface in the seven days after
    first profiling: the OpenAPI, llms.txt and both OAuth discovery documents were all 404 on 2026-08-03 and are all 200 now.
    The 2026-08-03 findings above are kept for the record and marked SUPERSEDED rather than rewritten. Note this also means
    the provider changed its public contract with no changelog and no status page to announce it.'
  findings:
  - surface: OpenAPI
    url: https://amuncore.com/openapi.json
    http_status: 200
    real: true
    note: OpenAPI 3.0.1, 5 operations over 2 paths, X-Api-Key security scheme, examples on all 30 responses. Byte-identical
      mirror at https://amuncore.com/swagger/v1/swagger.json.
  - surface: APIReference
    url: https://amuncore.com/swagger
    http_status: 200
    real: true
    note: Public Swagger UI, no sign-in required.
  - surface: LlmsTxt
    url: https://amuncore.com/llms.txt
    http_status: 200
    real: true
    note: 6.2KB, well-formed, and it publishes the twelve MCP tool names — the only anonymous route to the tool list, since
      tools/list itself is gated.
  - surface: WellKnown
    url: https://amuncore.com/.well-known/oauth-authorization-server
    http_status: 200
    real: true
    note: RFC 8414 metadata — authorization_code + refresh_token, PKCE S256 only, RFC 7591 dynamic client registration, single
      scope "mcp".
  - surface: WellKnown
    url: https://amuncore.com/.well-known/oauth-protected-resource
    http_status: 200
    real: true
    note: RFC 9728 metadata naming https://amuncore.com/mcp as the protected resource; the MCP 401 now carries the matching
      WWW-Authenticate Bearer challenge.
  - surface: AgentCard
    url: https://amuncore.com/.well-known/agent-card.json
    http_status: 404
    real: false
    note: Legacy /.well-known/agent.json also 404. No A2A agent card, so nothing was written to a2a/.
  - surface: SecurityTxt
    url: https://amuncore.com/.well-known/security.txt
    http_status: 404
    real: false
  - surface: GraphQL
    url: https://amuncore.com/graphql
    http_status: 404
    real: false
    note: security.html documents a GraphQL channel, but /graphql, /api/graphql and /api/v1/graphql all 404 — the GraphQL
      surface is generated per tenant, not served at the platform root.
  - surface: StatusPage
    url: https://status.amuncore.com/
    http_status: 0
    real: false
    note: DNS does not resolve. /changelog and /pricing also 404 — no status page, no changelog, and no standalone pricing
      route.
x-enrichment:
  date: '2026-08-10'
  status: enriched
  artifacts_added: 27
  artifacts_updated: 3
  pass: local-v1

AmunCore API — frequently asked questions

Does AmunCore have an API?

Yes. APIs.io lists 1 API from AmunCore, including AmunCore Dynamic API.

Is there an OpenAPI specification for the AmunCore API?

Yes. APIs.io indexes 1 OpenAPI specification for AmunCore, each linked for download from this page.

How do I authenticate with the AmunCore API?

AmunCore documents its authentication (apiKey/oauth2 · 3 schemes). The details are profiled on APIs.io as AmunCore Authentication.

How much does the AmunCore API cost?

AmunCore publishes its prices; its Free plan is $0 as of 2026-10-28. APIs.io lists 4 pricing plans for AmunCore, with each plan's price, limits and inclusions under Pricing on this page.

Does AmunCore have an MCP server?

Yes. APIs.io lists 1 MCP server for AmunCore: AmunCore is MCP-native by design: the REST endpoints a user builds over their own database become tools an AI assistant can call, under the same keys, permissions and audit trail. The MCP endpoint is

Is the AmunCore API ready for AI agents?

AmunCore has a Kin Score of 56.2 out of 100 (strong) and an Agent Readiness score of 56.5 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/amuncore"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/amuncore/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/amuncore/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.