<commit_before>---
layout: page
title:  "Agency API"
permalink: /agency-api/
---

...


## Notes on the API stack

* File formats - 'fixed', 'xls', 'xlsx', 'csv', 'json', 'geojson', 'ndjson`<commit_msg>first pass at API description<commit_after>---
layout: page
title:  "Agency API"
permalink: /agency-api/
---

The API itself is a simple, user-friendly API engine for an agency to use.  It resides at `https://api.agency.gov` and is managed by adding, overwriting, and deleting flat files in an Amazon S3 bucket.  

When a new file is uploaded into the bucket, an API is generated at `https://api.agency.gov/name-of-file`.  Each column header in the flat file results in a query parameter for the API.   

The [api.data.gov service](https://api.data.gov/about) is then used to offer API keys and track how developers use the API.  

Other details:   
* The file size limit is _____.  
* You can host up to _______ files.   
* Supported file formats are: 'fixed', 'xls', 'xlsx', 'csv', 'json', 'geojson', 'ndjson`

{'fraction_non_alphanumeric': 0.1252465483234714, 'fraction_numerical': 0.0009861932938856016, 'mean_word_length': 3.53125, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 3, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 1, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5749567', 'n_tokens_mistral': 330, 'n_tokens_neox': 319, 'n_words': 137}