Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Slice website screenshot

Slice

Slice is an Indian consumer fintech and small finance bank, founded in 2016 as SlicePay by Rajan Bajaj and headquartered between Bengaluru (corporate) and Guwahati (registered). The company originally built a buy-now-pay-later product and a prepaid-card-plus-credit-line offering aimed at students and young professionals — pitched as a credit-card alternative for India's Gen Z — and at its peak was reportedly issuing over 300,000 prepaid cards per month before RBI's 2022 restrictions on credit-linked PPI products forced a pivot. In October 2023 Slice announced a merger with the regulated North East Small Finance Bank (NESFB), the first fintech-into-bank merger in India; the merger received RBI approval in October 2023, CCI approval in March 2024 and NCLT (Guwahati) approval in August 2024, completed on October 27, 2024, and the combined entity was rebranded as Slice Small Finance Bank in May 2025. Today Slice operates a consumer mobile-first neobank — savings accounts, fixed deposits, UPI, a Slice credit card and rewards — alongside a merchant-facing payments stack exposed through a Merchant API (api.nebank.com) covering bank-account validation, payouts, pay-in/collect, refunds, virtual accounts, balance, transactions and webhook notifications. As of late 2024 the company had raised approximately $387M from investors including Tiger Global, Insight Partners and Blume Ventures.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Slice the way a machine reads it — 1 machine-readable artifact, 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 — Slice scores 16.7/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 16.7/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 2.6 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Banking & Open Finance 4.6 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Slice

Each block below is one kind of artifact we hold for Slice. 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.

Security Posture 1

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.

Slice Cards Domain Security

TLSv1.3 · HSTS · DNSSEC

SECURITY

Resources

Every other property we hold for Slice — 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.

Get Started 1

Portal, sign-up, and the first successful call

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 3

Status, limits, changes, and where to get help

← All providers · Data indexed from github.com/api-evangelist/slice-cards · machine-readable index on apis.io