How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Digby website screenshot

Digby

Digby was an Austin, Texas software-as-a-service provider of mobile commerce and mobile engagement solutions for large retailers, operating under parent company 30 Second Software Inc. Its platform — including the Localpoint location-based marketing product — delivered branded mobile web experiences and native shopping apps, connecting digital engagement to physical stores for customers such as Cabela's, Kohl's, Catalina Marketing and Hasbro. Digby raised venture funding from Battery Ventures, S3 Ventures, Daylight Ventures, Relay Ventures and the BlackBerry Partners Fund. The company was acquired by fellow Austin mobile company Phunware in May 2014 (along with its Movaya subsidiary in Seattle and Chengdu), terms undisclosed, and the Localpoint technology was folded into Phunware's product line. Digby no longer operates as an independent company: digby.com no longer resolves to a live site (last Internet Archive capture February 2015) and there is no current developer portal, documentation, API, SDK or other public API surface to catalog.

Digby is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.

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. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Resources

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

Other 2

Properties that don't map to a standard resource type

Digby is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.

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

Where this information came from

This is an independent, third-party profile of Digby, 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.