API archive entry · source-reported

TacoFancy

Community-driven taco database

Provider / source website

From the publisher

README & documentation

Source preview

Read the project’s overview, installation instructions and usage examples. The original README is the source of truth.

[](https://github.com/evz/tacofancy-api/actions) [](https://opensource.org/licenses/MIT) API for https://github.com/dansinker/tacofancy Visiting: /random/ will get you a random Base Layer, Mixin, Condiment, Seasoning and Shell. To just get a random full taco recipe, call it thusly: /random/?full-taco=true If you’d like to get info about the contributors for a certain recipe, you can call this endpoint: /contributors/:recipetype/:recipeslug/ So to get the contributors for the Delengua (Beef Tounge) Base Layer, do this: /contributors/baselayers/delenguabeeftongue Valid layer types are: baselayers, mixins, seasonings, condiments and shells. To…

evz/tacofancy-api on GitHub A short preview, not the full document.

Read the full README ↗ · Preview checked 2026-10-27T23:19:48.583Z

Inside the original README — Document outline
  1. TacoFancy API
  2. API Endpoints
  3. Random Taco
  4. Contributors
  5. Contributions
  6. Development Setup
  7. Docker (Recommended)
  8. Available Commands
  9. Environment Variables

Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.

Links from the README

References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.

Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.

Where these facts came from

AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Sep 14, 2026
  2. Last directory-field change: Sep 14, 2026
  3. Current source observation: Oct 30, 2026

Submit a source-backed correction

Source reference

public-apis/public-apis

This page separates source-reported facts from questions that need live provider verification.