From 1b5ff6ebfe7ab8cc580dca987893363614fc1104 Mon Sep 17 00:00:00 2001
From: mapsam <matthews.sam@gmail.com>
Date: Mon, 8 Jan 2018 12:04:15 -0800
Subject: [PATCH] core api functionality

---
 README.md | 51 ++++++++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 48 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 4a5e790..c17da1c 100644
--- a/README.md
+++ b/README.md
@@ -17,12 +17,57 @@ var MBTiles = require('@mapbox/mbtiles');
 
 # API
 
-### MBTiles utilities
+### Constructor
 
-**Constructor**
+All MBTiles instances need to be constructed before any of the methods become available. *NOTE: All methods described below assume you've taken this step.*
 
 ```javascript
 new MBTiles('./path/to/file.mbtiles', function(err, mbtiles) {
-  // mbtiles object
+  console.log(mbtiles) // mbtiles object with methods listed below
 });
 ```
+
+### Reading
+
+**`getTile`**
+
+Get an individual tile from the MBTiles table. This can be a raster or gzipped vector tile. Also returns headers that are important for serving over HTTP.
+
+```javascript
+mbtiles.getTile(z, x, y, function(err, data, headers) {
+  // `data` is your gzipped buffer - use zlib to gunzip or inflate
+});
+```
+
+**`getInfo`**
+
+Get info of an MBTiles file, which is stored in the `metadata` table. Includes information like zoom levels, bounds, vector_layers, that were created during generation. This performs fallback queries if certain keys like `bounds`, `minzoom`, or `maxzoom` have not been provided.
+
+```javascript
+mbtiles.getInfo(function(err, info) {
+  console.log(info); // info
+});
+```
+
+### Writing
+
+**`startWriting`** AND **`stopWriting`**
+
+In order to write a new (or currently existing) MBTiles file you need to "start" and "stop" writing. First, [construct](#constructor) the MBTiles object.
+
+```javascript
+mbtiles.startWriting(function(err) {
+  // start writing with mbtiles methods (putTile, putInfo, etc)
+  mbtiles.stopWriting(function(err) {
+    // stop writing to your mbtiles object
+  });
+});
+```
+
+**`putTile(z, x, y, buffer, callback)`**
+
+Add a new tile buffer to a specific ZXY. This can be a raster tile or a _gzipped_ vector tile (we suggest using `require('zlib')` to gzip your tiles).
+
+**`putInfo(data, callback)`**
+
+Put an information object into the metadata table. Any nested JSON will be stringified and stored in the "json" row of the metadata table. This will replace any matching key/value fields in the table.