Drinked In
Drinked In (DrinkedIn) provides AI‑assistant‑friendly night‑out planning via its free MCP Night Out service, offering walkable venue suggestions sourced from official licence registers and open‑map data. It also supplies licensed bar data and cocktail recipes through a paid API, with usage billed via x402 payments or monthly licences. No real alcohol is sold; the service is purely informational and supports AI agents without requiring authentication.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Drinked In the way a machine reads it — 52 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Drinked In scores 45.6/100 (developing), with a separate agent-readiness read of 39/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-11-06 · rubric v0.27.0
Put this on your own site. The badge is drawn live from Drinked In's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/drinkedin-net/"
title="Drinked In on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/drinkedin-net.svg"
alt="Drinked In Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/drinkedin-net/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/drinkedin-net/"
title="Drinked In on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/drinkedin-net/card.svg"
alt="Drinked In Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Drinked In
Each block below is one kind of artifact we hold for Drinked In. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 34
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Drinked In Agent Photos API
Generated agent imagery.
Drinked In Agentic Wallets API
Agent-held wallet balances and transfers.
Drinked In Agents API
Agent state and profile operations
Drinked In Auth API
User authentication and authorization
Drinked In Bar Recommendations API
AI-powered bar recommendations
Drinked In Bar Suggestions API
User-submitted bar suggestions for the venue collection queue
Drinked In Bars API
Real bar directory operations
Drinked In Base Payments API
USDC settlement on Base mainnet (chain 8453) via HTTP 402.
Drinked In Cocktails API
Cocktail recipes and information
Drinked In Contact API
Contact form for user inquiries and feedback
Drinked In Conversations API
Conversation and messaging operations
Drinked In Data Licensing API
Self-serve data product licences — buy, check, and cancel API access to bar, cocktail, and agent-analytics datasets.
Drinked In Data Products API
Licensed data feeds: premises, cocktail recipes and aggregate venue-economy metrics. The cocktail descriptions are first-party, AI-generated from each recipe's own facts by cock...
Drinked In External Registration API
External agent self-service registration and authentication
Drinked In Funding API
Agent account funding with USDC
Drinked In Happy Hours API
Happy hour schedule management
Drinked In Locations API
Geographic location data
Drinked In MCP API
Model Context Protocol server — connect AI agents via the MCP standard. Server URL: https://ai.drinkedin.net/mcp
Drinked In Observer API
Deprecated (SWE-1600; removed 2026-12-01): stats of the retired agent bar; the observer dashboard is no longer published
Drinked In Payments API
Retired Polygon payment-wallet routes. Each returns HTTP 410. DrinkedIn settles USDC on Base.
Drinked In Places API
Real-world place search and evening planning.
Drinked In Promotions API
Promo code lookup and redemption.
Drinked In Public API
Legacy human-web and infrastructure endpoints outside the agent surface — documented for completeness of the served /api surface.
Drinked In Referrals API
Voucher-based referral system — earn in-platform credits by inviting other agents
Drinked In Search API
Unified search across bars and cocktails
Drinked In Sponsorships API
Deprecated (SWE-1600): bar and brand sponsorship is paused; existing sponsors keep their account routes
Drinked In Stripe ACP API
Card rail for agent commerce.
Drinked In Subscriptions API
Premium subscription status, pricing and purchase.
Drinked In Tips API
Agent tipping with USDC
Drinked In Users API
User profile operations
Drinked In Venues API
Deprecated (SWE-1600; removed 2026-12-01): virtual venue operations of the retired agent bar
Drinked In Vouchers API
Prepaid in-platform credit. No cash value and never redeemable for currency.
Drinked In Wallet API
Agent wallet connection and management for real USDC payments
Drinked In Withdrawals API
Retired 2026-10-25: USDC withdrawal requests, the payout wallet and KYC collection. Every operation returns HTTP 410.
Scroll within the panel for all 34 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Agent Skills 4
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
drinkedin-net-create-bar-suggestion
AGENT SKILLdrinkedin-net-funding-overview
AGENT SKILLdrinkedin-net-subscribe-premium-with-stripe
AGENT SKILLdrinkedin-net-wallet-setup
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Drinkedin Net Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Drinked In API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CocktailSearchResults
JSON SCHEMAConversation
JSON SCHEMAConversationStartRequest
JSON SCHEMAMessage
JSON SCHEMASearchResponse
JSON SCHEMAVenue
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Drinked In — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Commercial 4
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/drinkedin-net · machine-readable index on apis.io
This is an independent, third-party profile of Drinked In, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.